something fishy is going on with Travis

seeing a bunch of test failures:
https://travis-ci.org/expressjs/compression/jobs/87724011
https://travis-ci.org/expressjs/compression/jobs/87722737
https://travis-ci.org/expressjs/compression/jobs/87724016
https://travis-ci.org/expressjs/compression/jobs/87724018
blocking: https://github.com/expressjs/compression/pull/62

Please file this on travis-ci directly - the error messages imply that travis can't reach iojs.org - likely due to an SSL change on their end.

yep sounds good. thanks


Early Suggestions

There is no readme file on root, add it and add from there to your configuration wiki page please, also to other important pages.

There is no Linux configuration path displayed on configuration wiki page, I found it here
~/.local/share/Colossal Order/Cities_Skylines/ModConfig/reddit-for-chirpy.txt

Also please add link to the chirp filter mod on readme page as recommened mod.

I've done 1 and 2, not too sure about the third thing mentioned.
I've started working on a little bit of work in regards of replacing the default messages at https://github.com/mabako/reddit-for-city-skylines/commit/e00ab5a51327ba674477a9276097f464af6fd4dd and this, by extend, means it'll be incompatible to the chirp filter if I publish it.

Thanks :+1: closing


Nano-style on-screen help by default

Thanks a lot for the project. It's already at the top end of Linux bluetooth interfaces I have used in terms of comfort for me. I wonder whether it would be possible to display the keybindings by default like nano does? An equivalent of -x and set nohelp could be added.

It can be implemented, but my only concern is that is could eat up screen space, especially since there are a lot of keybindings for a single screen. Wouldn't pressing the Help key suffice?

For me, I am occasionally using this software and so will never remember the keybindings. Of course if you prefer to put the bindings behind a help key that's still more convenient than reading documentation, but while it is very much your choice, I would make attempt to make an argument that the common user is a less frequent users and would thus be best served by the nano-style on-screen help that is easily hidable.

Fair argument, and I will consider implementing this. As stated before, since there are a lot of keybindings for just one screen, and I do not want to use screen space unnecessarily, this will require some contemplation.
Maybe the main/commonly used keybindings to facilitate basic operations can be suggested to the user for each screen, I will have to check and run some tests. If you have any ideas on how to implement this, preferably with a PR or screenshots, do submit them, as they can be helpful in implementing this feature.

I believe nothing more than navigation, connect/disconnect, the menu ( shortcuts? Well the bindings to show the menus ) and ofcourse the help binding should be shown.
The nagivation buttons should be concise as they will otherwise take up a huge amount of space; possibly it could be shown as this: ←/↓/↑/→ =  h/j/k/l or possibly ←h/↓j/↑k/→l or maybe replace the arrows with L D U R incase we shouldn't use unicode.
maybe we could display the arrows/letters/words under the bindings, like on another row?
h j k l
< ^ ˇ >

@frankier @hacktail, how does this look? Would this suffice? A similar set of limited help keybindings will be present on the file picker and the progress view as well.

@frankier @hacktail, how does this look? Would this suffice? A similar set of limited help keybindings will be present on the file picker and the progress view as well.

Looks amazing

This will be implemented in the next release, and any modifications to the help display can be further suggested by reopening this issue once it is closed.

This feature has now been implemented and enabled by default, and can be disabled by:

Using the command-line option --no-help-display
Setting the configuration parameter no-help-display: true

Thanks a lot. It looks great!


[zh] Localize /feature-gates/b*.md

Related to issue #44410 . Localize b*.md files:

balance-attached-node-volumes
block-volume
bound-service-account-token-volume

/lgtm


how to get the 7 cytoarchitectonic classes of the von Economo atlas

Hi～
Now I only get this information from the paper: An MRI Von Economo – Koskinas atlas , but i do not know how to get the 7 cytoarchitectonic classes of  the von Economo atlas, just like you did in this interesting paper!  could you tell me how to do it, or how to get extra infomation?  Thank you!!

Hi,
The mapping of cortical ROIs to von Economo cytoarchitectonic classes was originally performed by my colleagues, as described here https://royalsocietypublishing.org/doi/10.1098/rstb.2015.0362#d3e722 (section "(d) Parcellation into cytoarchitectonic classes").
The labels for the 308 cortical ROIs used for analysis in the study related to this repository are available with the remainder of the data here: https://www.repository.cam.ac.uk/handle/1810/263627 - however, access to this data has to be requested.
Alternatively, the same labels were used as part of another study, and are available here: https://github.com/SarahMorgan/Morphometric_Similarity_SZ (file "vonEcon_500_overlap.txt")
Finally, this study https://www.pnas.org/content/117/6/3248 used the same cytorachitectonic classes, but as mapped to the 360-ROI multi-modal parcellation by Glasser et al - these labels are available here https://figshare.com/articles/Data_for_Conservative_and_disruptive_modes_of_adolescent_change_in_human_brain_functional_connectivity_/11551602 (variable "ve.id.subc" in the file "nspn.fmri.general.vars.RData" - where the first 16 values correspond to subcortical regions, labeled as "8", and the remaining 360 values to the crotical ROIs of the Glasser et al atlas).
As a final note, these classes are different from the ones in the paper "An MRI Von Economo – Koskinas atlas".
I hope this helps!
Frantisek

This helped me. Thank you for your detailed answer!
Next, I want to read your very interesting articles carefully, thank you for sharing.
Lianglong Sun


Preparing metadata (pyproject.toml) did not run successfully. (release 1.0.0)  (maybe NUMPY 2.0.0 problem)

Just setting up a nice new PiZero 2 using 32bit bookworm (lite) because I had a nice email this new version had been released :-)
Using Raspberry Connect - terminal to do all the remote stuff, but used SSH before that.
Only other extra program installed is git itself (it's not installed by default on lite) and of course RPi Connect
Just flagging this up, could be your problem, or it might not be.
I get the error twice, first in initial setup and then when it tries to get example dependencies.
Is this because Numpy is too new (2.0.0 has only just been released six days ago, 17th Jun 2024)
Collecting numpy
  Using cached numpy-2.0.0.tar.gz (18.3 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Installing backend dependencies ... done
  Preparing metadata (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Preparing metadata (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [23 lines of output]
      + /home/weatherhat/.virtualenvs/pimoroni/bin/python /tmp/pip-install-5hg1d__a/numpy_e78cb89d51894ade9e9e7577acd5bf6e/vendored-meson/meson/meson.py setup /tmp/pip-install-5hg1d__a/numpy_e78cb89d51894ade9e9e7577acd5bf6e /tmp/pip-install-5hg1d__a/numpy_e78cb89d51894ade9e9e7577acd5bf6e/.mesonpy-487gv4t1 -Dbuildtype=release -Db_ndebug=if-release -Db_vscrt=md --native-file=/tmp/pip-install-5hg1d__a/numpy_e78cb89d51894ade9e9e7577acd5bf6e/.mesonpy-487gv4t1/meson-python-native-file.ini
      The Meson build system
      Version: 1.2.99
      Source dir: /tmp/pip-install-5hg1d__a/numpy_e78cb89d51894ade9e9e7577acd5bf6e
      Build dir: /tmp/pip-install-5hg1d__a/numpy_e78cb89d51894ade9e9e7577acd5bf6e/.mesonpy-487gv4t1
      Build type: native build
      Project name: NumPy
      Project version: 2.0.0
      C compiler for the host machine: cc (gcc 12.2.0 "cc (Raspbian 12.2.0-14+rpi1) 12.2.0")
      C linker for the host machine: cc ld.bfd 2.40
      C++ compiler for the host machine: c++ (gcc 12.2.0 "c++ (Raspbian 12.2.0-14+rpi1) 12.2.0")
      C++ linker for the host machine: c++ ld.bfd 2.40
      Cython compiler for the host machine: cython (cython 3.0.10)
      Host machine cpu family: arm
      Host machine cpu: armv7l
      Program python found: YES (/home/weatherhat/.virtualenvs/pimoroni/bin/python)
      Found pkg-config: /usr/bin/pkg-config (1.8.1)
      Run-time dependency python found: YES 3.11
      Has header "Python.h" with dependency python: NO

      ../meson.build:44:2: ERROR: Problem encountered: Cannot compile `Python.h`. Perhaps you need to install python-dev|python-devel

      A full log can be found at /tmp/pip-install-5hg1d__a/numpy_e78cb89d51894ade9e9e7577acd5bf6e/.mesonpy-487gv4t1/meson-logs/meson-log.txt
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
⚠ WARNING: ^^^ 😬 previous command did not exit cleanly!

It seems PiWheels cannot cope with NUMPY 2.0.0 on Python 3.11 either, hence it's trying to build.
https://www.piwheels.org/project/numpy/


Using Hyn tenancy with Laravel-admin

@z-song

Laravel Version: 5.5
PHP Version: 7.2
Laravel-admin: latest

Description:
I am using  package for multi tenancy.
https://laravel-tenancy.com/documentation/introduction/configuration
I could not change admin tables connection to the tenant connection.
If there any possible way to change this?
Even changing the connection in admin.php (config) some model use the default db connection.

Yes, I am looking for it too!!
@pcfjojo do you have any idea of it?

@geekstek

I copied admin folder
I put all admin related migration without passing the connection.
Also I have all basic insert query for create an admin.

That's it.

@pcfjojo Thank you for your share, I try your solution now, Thanks a lot!!

@pcfjojo are you use laravel-admin for tenant db? or both (double laravel-admin for system and tenant)?

No My tenent has it own admin panel and user. I dont use admin panel for system.

Got it, thank you for your sharing :)


Edit 'Supporting legacy code' example/description

Specifically:

Rewrite the code sample to drop the transaction
Rewrite the surrounding text to note that there may be a brief window after the rename but before the view creation where your application may need to do some error handling (which in theory it is already doing when accessing the DB)
Link to the relevant section of the "known limitations" page

Fixes #2555

Also related to the above, do you think it is reasonable to provide more information about how long one should expect the gap to be between the table rename and the subsequent view creation?

The gap should generally be on the order of the latency of the slowest network link between two nodes in the cluster, but can be minutes if a node had crashed.
I think the only thing we can say is that, once the CREATE VIEW succeeds, further queries should work.

Review status: 0 of 3 files reviewed at latest revision, all discussions resolved, all commit checks successful.

v2.0/views.md, line 164 at r1 (raw file):

~~~

### Simplify supporting legacy code

My preference would be to get rid of this section altogether. I don't think it's particularly valuable.
For anything other than a rename of the original table, queries through the view will likely be too slow to claim that the app just works anyway.

v2.0/views.md, line 186 at r1 (raw file):

~~~

Note that there will be a brief window of time after the table rename and before the view creation when there will be no relation (table or view) called `user_accounts`. During this window, if your application tries to access `user_accounts`, it will need to handle any error that occurs. In most ORMs, this will cause an exception to be thrown, followed by a retry. Once the view is created, the retry should succeed, and further accesses of `user_accounts` will work as expected.

do we use the word "relation" anywhere else in our docs?

v2.0/views.md, line 186 at r1 (raw file):

~~~

Note that there will be a brief window of time after the table rename and before the view creation when there will be no relation (table or view) called `user_accounts`. During this window, if your application tries to access `user_accounts`, it will need to handle any error that occurs. In most ORMs, this will cause an exception to be thrown, followed by a retry. Once the view is created, the retry should succeed, and further accesses of `user_accounts` will work as expected.

I think "followed by a retry" is unclear. No ORM will just retry on such an error. The client needs to retry... Which is unlikely - it's weird to suggest to do retries on schema errors.
I wouldn't say anything about retries.

Comments from Reviewable

v2.0/views.md, line 164 at r1 (raw file):
Previously, andreimatei (Andrei Matei) wrote…
My preference would be to get rid of this section altogether. I don't think it's particularly valuable.
For anything other than a rename of the original table, queries through the view will likely be too slow to claim that the app just works anyway.

This is good input, @andreimatei. I stole this use case from other dbs' docs on views and assumed it was valuable, given that the alternative is interrupting the app for the duration of the schema change. But I defer to you on this.

Comments from Reviewable

Review status: 0 of 3 files reviewed at latest revision, 3 unresolved discussions, all commit checks successful.

v2.0/views.md, line 164 at r1 (raw file):
Previously, jseldess (Jesse Seldess) wrote…
This is good input, @andreimatei. I stole this use case from other dbs' docs on views and assumed it was valuable, given that the alternative is interrupting the app for the duration of the schema change. But I defer to you on this.

if we had support for atomic renames + create view, I'd be cool to showcase it. But since we don't, I think this section is adding little.

Comments from Reviewable

v2.0/views.md, line 164 at r1 (raw file):
Previously, andreimatei (Andrei Matei) wrote…
if we had support for atomic renames + create view, I'd be cool to showcase it. But since we don't, I think this section is adding little.

Cool. Let's just remove then, @rmloveland. Sorry for causing you unnecessary effort here.

Comments from Reviewable


Support more Java trigger templates

Start from Maven Azure Functions plugin: 1.0.0-beta-3, users can add more Java trigger templates, including:

EventGrid
EventHub
Cosmos DB
Service Bus Queue
Service Bus Topic

For short-term plan, check the pom and get the version of the plugin to determine which templates are available.
For long-term plan, we will check the possibility to add Java templates into the tooling feed and consume the templates directly from the feed.
@EricJizbaMSFT What do you think?

I would really prefer if we came up with a long-term solution rather than another workaround. If we had fixed https://github.com/Microsoft/vscode-azurefunctions/issues/84 anytime between now and last November, users would've automatically gotten all of these templates already. I think this is a great catalyst to get that work done.
Adding the templates to some sort of feed is an option. However, would it be possible for maven or the plugin itself to output information about the templates?

@pragnagopa @soninaren
Eric proposed another solution that the templates & metadata still stored in Maven plugin, and the plugin will have another command to output the templates information itself. (@EricJizbaMSFT Correct me if I misunderstood). This could easily solve the version control problem and looks easier to achieve than adding templates to tooling feed.
Please let me know your thoughts. Personally I vote for this solution.

@jdneo
I agree with Eric proposed solution, We should add a list-templates command / functionality to the maven plugin, it would provide templates and related metadata as a json. We should also with the maven plugin version to the cli-feed, the VS Code can check the users machine to verify if the right version of maven plugin is installed, and can warn users if it does not match. I will add the plugin version to the cli-feed as soon as the plugin update is ready.

PR for Maven plugin: https://github.com/Microsoft/azure-maven-plugins/pull/310

@EricJizbaMSFT PR updated, please take a look when you have time :)


Release 0.1.14

0.1.14 (2020-09-09)
Release highlights
This release includes mainly bug fixes and changes to the UI so it is more consistent across different components.
Changelog
Bugfixes 🐞

TipRecord: send report doesn't work if the user is not logged in (#782)
Avoid redundant navigation to current location TipRecord, TipComment (#777)
Three dot menu Claim not working with integrated wallet (#764)
The scrolled position is lost if you click on other navigation, then click Tips in navigation (#715)
The updating of the profile image is broken (#773)
Scrolling of tips doesn't work properly(#758)
TipList: remove duplicate TipsPagination (#762)
Fix scrolling (#763)
Fixed minor bug in nested comments (#785)

Features ✨

Spanish translation (#786)

Maintenance 🚧

Fix errors, warning on init load (#759)
Update SDK to 7.7.0 (#761)
Update dependencies (#757)
Extract constants (#768)
Refactoring (#771 && #793)
eslint: force pascalCase across components (#775)
Change prop type in Link component (#776)

Other changes💡

Make AuthorAndDate component looks the same in all cases (#779)
The maintenance page is too big on iPhone 6/7/8 and is not scrollable (#725)
TipRecord: Show the claim button only if an address is available (#766)
Refactor all modals and popups to be consistent (#783)

Test Protocol: https://nx3594.your-storageshare.de/f/769411

Test protocol: https://nx3594.your-storageshare.de/f/769411


[6.x] Normalize scheme in Redis connections

Description
This PR attempts to improve the consistency between Predis and PhpRedis drivers regarding the configuration of the scheme.
Current behavior
By default both drivers are connecting to the Redis server using tcp. It is possible to configure the scheme but each driver requires a different setup:

The Predis client accepts a scheme key in the $parameters array of its constructor. E.g. 'scheme' => 'tls'.
The PhpRedis client needs to have the scheme prefixed to the $host string of its constructor. E.g. tls://<IP_ADDRESS>.

In Laravel that means we have to use different configurations in database.php:
// predis
'default' => [
    'scheme' => 'tls',
    'host' => '<IP_ADDRESS>',
    'port' => '6379',
]

// phpredis
'default' => [
    'host' => 'tls://<IP_ADDRESS>',
    'port' => '6379',
]

Since #33800 was merged, it is possible to define the scheme using the url key for phpredis. The url being parsed transforms the host in the correct format as tls://<IP_ADDRESS>:
// phpredis
'default' => [
    'url' => 'tls://<IP_ADDRESS>:6379',
]

But using the url key for the predis driver results in a connection error, because the host is again formatted as tls://<IP_ADDRESS> but the client has its scheme as tcp internally, so it tries to connect to tcp://tls://<IP_ADDRESS>:6379 which is invalid.
Proposed changes
With this PR, it is possible to use the scheme key as well as the url key for both drivers, thus improving the consistency in the configuration and allowing to switch drivers more easily:
// scheme using url (predis / phpredis)
'default' => [
    'url' => 'tls://<IP_ADDRESS>:6379',
]

// scheme using key (predis / phpredis)
'default' => [
    'scheme' => 'tls',
    'host' => '<IP_ADDRESS>',
    'port' => '6379',
]

Instead of formatting the host in RedisManager like the aforementioned PR does, it assigns the scheme key in the configuration, which will be handled in the connectors: The PredisConnector will pass it to the client's constructor, and the PhpRedisConnector will format the host using the scheme if it was defined in the configuration or parsed from the url.
This change has no breaking changes, as it follows the functionality of the previous PR, allowing redis:// protocols as well as tcp:// and tls:// in the url key. It's also compatible with the existing functionality regarding the scheme key for the predis driver.
Summary

Add support for defining the scheme in  the url key for predis
Add support for defining the scheme key for phpredis
Functionality for defining the scheme in the url key for phpredis remains the same
Functionality for defining the scheme key for predis remains the same
All functionality also apply to clusters
Add tests asserting both drivers are connecting correctly with scheme or url
Add test asserting the ConfigurationUrlParser returns the correct driver for Redis URLs with scheme

@sebdesign this seems to have broken some things. See https://github.com/laravel/framework/issues/34018 & https://github.com/laravel/framework/pull/34017
Can you please take a look at this?

@driesvints I'll look into it right now.


Allow passing popperProps. Fixes #1525

Adds the ability to send props to the Popper component

Nice work!

Thanks.
Wow that was quick 😊
What's the plan for publishing a new version to npm?

Will try to get a new version out today


CON-3568 add policy subcommand

https://github.com/conjurinc/api-ruby/pull/87 needs to be merged first.
Also, Patch GLI so it will hide subcommands hidden with #hide_docs.

The change from JSON to a Hash happens here:
https://github.com/conjurinc/api-ruby/blob/master/lib/conjur/api/ldapsync.rb#L47
On the service side, the creation of the JSON message happens here:
https://github.com/conjurinc/ldap-sync/blob/master/lib/api/helpers.rb#L81
On Thu, Nov 17, 2016 at 9:36 AM, Kevin Gilpin<EMAIL_ADDRESS>wrote:

@kgilpin commented on this pull request.
In lib/conjur/command/ldapsync.rb
https://github.com/conjurinc/cli-ruby/pull/159#pullrequestreview-9036277
:

       else

       jobs = jobs.map{|j| j[:id]} if options[:'ids-only']

       display(jobs)

       exit_now! resp['error']['message']

@apotterri https://github.com/apotterri on the API side, where do the
errors get collected into this field?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/conjurinc/cli-ruby/pull/159#pullrequestreview-9036277,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEBHAyV3QGjBW-kdKegyewW5tq_TIDdXks5q_GZxgaJpZM4KzKlF
.

--
Alan Potter
Engineer
p:<PHONE_NUMBER>
http://t.yesware.com/tt/58d6ef3f2477232db08043fa9198ec0f5a0fde51/f59ded25d9f0fae3e973353a29205cf4/5ff664c66c5990e35bd8d1f3bfc0b483/www.conjur.net/
Identify, Authorize, Audit... Everything
Demo
http://t.yesware.com/tt/58d6ef3f2477232db08043fa9198ec0f5a0fde51/f59ded25d9f0fae3e973353a29205cf4/13deaa1654e874c3dccc0acce4e70193/t.sidekickopen03.com/e1t/c/5/f18dQhb0S1KL8bGch0W2n0x6l2B9nMJW7t6jwn3LqWkjN2BgL6d1vVSKf69FLZ203?t=https%3A%2F%2Finfo.conjur.net%2Fdemo&si=3680029&pi=47d6aafc-d455-4a13-9ffc-a8737ef09b32
| Resources
http://t.yesware.com/tt/58d6ef3f2477232db08043fa9198ec0f5a0fde51/f59ded25d9f0fae3e973353a29205cf4/cc9a5a824c8143be8a0bab0dcc7f1c20/t.sidekickopen03.com/e1t/c/5/f18dQhb0S1KL8bGch0W2n0x6l2B9nMJW7t6jwn3LqWkjN2BgL6d1vVSKf69FLZ203?t=https%3A%2F%2Finfo.conjur.net%2Fresources&si=3680029&pi=47d6aafc-d455-4a13-9ffc-a8737ef09b32
| Blog
http://t.yesware.com/tt/58d6ef3f2477232db08043fa9198ec0f5a0fde51/f59ded25d9f0fae3e973353a29205cf4/c59449660ac6f9ab10a1787fd5988490/t.sidekickopen03.com/e1t/c/5/f18dQhb0S1KL8bGch0W2n0x6l2B9nMJW7t6jwn3LqWkjN2BgL6d1vVSKf69FLZ203?t=https%3A%2F%2Fblog.conjur.net%2F&si=3680029&pi=47d6aafc-d455-4a13-9ffc-a8737ef09b32


Error when run demo

Hi, i follow guide at https://stackoverflow.com/questions/3934508/printing-a-formatted-html-page-in-c-sharp
When i set:
info.Arguments = $"-p "{printer}" "-l 0" "-t 0" "-r 0" "-b 0" "{string.Join("" "", urls)}"";
I get a error: HTML page failed to load
If i just write: info.Arguments = $"-p "{printer}" "{string.Join("" "", urls)}"";
Print normal
Please help me, i want set content margin to print, thank in advance.

Try this:
info.Arguments = $"-l 0 -t 0 -r 0 -b 0 -p "{printer}" "{string.Join("" "", urls)}"";

Many thanks :+1:
I got it.


[draft] feat(atenlib): add ops (any)

A couple of questions: why not use ReduceMax instead of ReduceSum ? Is it because of opset dependence?
Also: does ReduceSum not work for scalar inputs? I am wondering where exactly the logic breaks (with onnx.ORT) if a zero-dimensional tensor is used.


The date cannot be manually modified yet.

Waiting for a fix from Martin. You should be able to click on the date property and pick a new one, but there is a bug and it disappears.

@bjsi , it not just disappears, but it creates a flashcard:


In some regions, monday is the first day of the week

Gitea version: 1.7.1, from single binary.
The high-level contribution overview starts the week at sunday. I'd prefer to make it start on monday and have sunday the bottom, as a feature-request.

I'd prefer to have this configurable as the week starts in some countries on monday while in others on sunday.

From me tinkering with this for a bit:
While the module we use allows us to change the order of the days of the week, the squares do not seem to change accordingly to match, which unfortunately means this feature may have to first happen upstream...

So this depends on WildCodeSchool/vue-calendar-heatmap#1 right?

@Oreolek Yeah pretty much.

Is any work being done on this? +1

any update?

This depends on upstream library to add such option so this should be asked in it

upstream reference with a PR: https://github.com/julienr114/vue-calendar-heatmap/pull/14

Any chance for this feature? our start days are saturdays

I'd just like to point out that Monday being the first day of the week isn't just in some regions - it's international, as in ISO - the standards organization - not just ISO 8601. If anything, that should be the default and, if not, then configurable at the very least.

I'm waiting

Note that https://github.com/go-gitea/gitea/commit/04e97b83115e7439d43c0ede5fe2d1b50d201c52 changed the library to an updated one, I opened a new issue there: https://github.com/razorness/vue3-calendar-heatmap/issues/19

Looks like heatmap control is abandoned one. There is a PR with fix, but still.

In some regions

I'll clarify you: in MANY regions, the more than a half of countries in the world uses Monday as a start of week. Also the fact: Bandgladesh begins week with Friday, and seven countries (United Arabic Emirates, Bahrein, Jibuty, Algir, Egypt, Marokko, Sudan) do begin a week with a... Saturday!


$ref '/definitions/HProperties' in 'vscode://schemas/settings/user' can not be resolved.

See https://github.com/Microsoft/vscode/issues/57460:
ll of a sudden I am getting this warning on all of my settings.json files.
$ref '/definitions/HProperties' in 'vscode://schemas/settings/user' can not be resolved.
This occurs even in latest insider build. Line 1 at { in the Settings.json

I reproduce by installing the latest version of VSCodeBeautify.
Likely caused by this line: https://github.com/HookyQR/VSCodeBeautify/blob/97790c4da01aad6d5bab8562c0ffdd3ddd16bd7d/package.json#L164
I advise against to use of $ref in settings definition. Please keep the settings simple.

@aeschli Thank you for finding the issue. Meanwhile I will disable this extension till this issue is resolved.

Same here. Disabling "Beautify" extension made the error go away. Hopefully, it will be resolved soon.

Instead of disabling the extension completely, you could just add this to your user settings -
I just removed the json and jsonc from the file types settings in vscode...then the error went away.
 {     "js": {       "type": [         "javascript",          "json",      // remove this line          "jsonc"    // and remove this line (i removed it because i don't ever use this file extension)       ],       "filename": [         ".jshintrc",         ".jsbeautifyrc"       ]     },     "css": [       "css",       "scss"     ],     "html": [       "htm",       "html"     ]   }
then save your settings and the problem message goes away...

Above solution didn't fix for me, neither did removing all custom Beautify settings including .jsbeautifyrc

Bump.
Same issue.

same here & today,..

Same here. Please fix Asap..................................

@aeschli you advised against loading remote schema via $ref. I can see now that, despite following the spec when loading a schema for a file type, it just doesn't play nice inside the VS Code settings file. I'll simply remove all hints, as including them all nicely just won't be supported by the controlling system.

Pull requests are nice BTW people.


TransferManager callbacks

Confirm by changing [ ] to [x] below:

[X ] I've gone though Developer Guide and API reference
[X ] I've searched for previous similar issues and didn't find any solution

Platform/OS/Hardware/Device
What are you running the sdk on?
Android - AWS SDK 1.8.2
Describe the question
Transfer Status and error callbaks
I've noticed that for a given file upload in progress, had the device experience networking issues (sudden loss of connectivity) the transfer status callback and error callbacks are called multiple times reporting the same status:  for example the error callback reports many NETWORK_CONNECTION errors and the transfer status callbacks reports multiple STATUS_FAILED statuses. Now I suppose this multiple notifications happen because the upload in reality it's a multipart upload so each callback it's triggered from the relative upload part. My question is: can I be notified for the overall process rather than for each single part ?
When things goes well and the transfer is succesful I  get notified with a single status COMPLETED. Why this is not happening for a non successful transfer ?  Can it be achieved ? Or Am using wrongly the API ?
I wouldn't expect to use TransferHandle::WaitUntilFinished to understand that the transfer ended giving I'm relying on callbacks. Am I right in thinking this ?
Thanks in advance

Hi @nakkore ,
I would have to know more about your use case to know for sure, for example, it might be retrying (and failing) to reconnect a bunch of times.
Could you show me your debug logs (make sure to sanitize them of private info)?

Hi sure,
to exclude retries I've configured config.retryStrategy = std::make_sharedAws::Client::DefaultRetryStrategy(0);
I'm not doing any retries in the code.
I've attached the relevant log when the first sequence of errors start which happens when, while there's an upload in progress, I put the phone in flight mode.
aws.log
Hope it helps.
P.S.
I had to remove from CurlHttpClient.cpp::CurlDebugCallback the debug print which prints the buffer as it was generating non useful noise (else branch). Would it be more useful if it optionally printed an hexdump instead ?

@KaibaLopez did you have a chance to check the log please ?

sorry for the slow updates @nakkore , but yea regarding the questions:

can I be notified for the overall process rather than for each single part ?

I guess it depends on what you mean by "notified" ? The Trace logs will happen for each part, because each part is a different request, which gets a response, this is true for successes too btw.... but just the same way you get a TransferStatus::COMPLETE,for successful calls, you can get TransferStatus::FAILED once its all done.

I wouldn't expect to use TransferHandle::WaitUntilFinished to understand that the transfer ended giving I'm relying on callbacks.

I'd still use TransferHandle::WaitUntilFinished.... you don't really HAVE to I guess but then it's up to you to know when all the threads working on the upload are finished, all that the function does is having a semaphore wait for a signal anyway so you can do that yourself on your callbacks.
Sorry about the earlier confusion and let me know if I misunderstood something about your questions again.

Thank you @KaibaLopez. You correctly say that I get one TransferStatus::COMPLETE for the overall transfer and that's true but the same doesn't apply for the TransferStatus::FAILED where, instead, I receive multiple calls: see my first comment and that's the point of my report.
By "notified", sorry If I wasn't clear enough, I meant that the callback is triggered. To make things clearer I'm referring to the transferStatusUpdatedCallback and errorCallback which are configured in TransferManagerConfiguration.
For example and to be more precise the FAILED callback, when the transfer fails in my case, is triggered at TranferManager.cpp line 409 (in DoMultiPartUpload) but also at TranferManager.cpp line 533 (in HandleUploadPartResponse) and line 588 (in HandleUploadPartResponse). So it's not happening once as I expected and as you've stated but it's happening multiple times.
If I've understood correctly the code the FAILED for the overall transfer should be the one raised in DoMultiPartUpload . The other unexpected FAILED calls come from HandleUploadPartResponse.
For reference line numbers refer to the 1.8.15 SDK.
I hope it's clearer.
P.S
For the use of WaitUntilFinished:
In my mind If I used WaitUntilFinished it means that I want to block until I get a result making, de facto, the calls to UploadFile/DownloadFile blocking. By using WaitUntilFinished I don't see the point using callbacks If I have to wait.
If I used only callbacks it means that I don't want to block and I want to be "notified" when the transfer completes or errors.

Hi @nakkore ,
So there's a few things here:

If I've understood correctly the code the FAILED for the overall transfer should be the one raised in DoMultiPartUpload . The other unexpected FAILED calls come from HandleUploadPartResponse.
I mean, I wouldn't say unexpected, each part is a unique "upload" so it is important to know the response to each, specially if it failed. But yea the overall comes from DoMultiPartUpload.

You correctly say that I get one TransferStatus::COMPLETE for the overall transfer and that's true but the same doesn't apply for the TransferStatus::FAILED.

This is the part that's confusing, I can see in the logs you provided, the very last line states a change to the update handle status to Failed, that is the status of the overall call.
But I can see also that the update handle to FAIL status change happens twice, which is kind of weird, I was also able to reproduce this so I'll look into it a bit, I think it's related to the last "batch" of async calls, but I'd have to dig a bit further to be sure.
Finally, Regarding WaitUntilFinished, I think we are kind of in agreement that it is up to you when to use the semaphore/mutex but:

In my mind If I used WaitUntilFinished it means that I want to block until I get a result making, de facto, the calls to UploadFile/DownloadFile blocking

True, the calls would be blocking, but they kind of have to be since they are multi threaded operations at some point you need to coincide...Now this doesn't mean you have to be waiting right after the upload call, so the point of the callbacks is that you can do other stuff while that is happening, you just need to block (via your own semaphore/mutex or calling WaitUntilFinished) before you try to access the response/outcome and/or before you try to exit the application, here's a quick example of what I mean:
    auto uploadHandle = transferManager->UploadFile(file, bucket , name, "text/plain", Aws::Map<Aws::String, Aws::String>());

/* here you can do other stuff unrelated and with no access to uploadHandle , and this could be the bulk of your code so long as you don't touch uploadHandle it should be safe*/

    uploadHandle->WaitUntilFinished();
    bool success = uploadHandle->GetStatus() == TransferStatus::COMPLETED; // to get this you need to know the threads have all ran their course so you need to block the callbacks.
    if(success){/*do more stuff that's related to the uploadHandle result*/}
    else{/*get error or whatever*/}

    Aws::ShutdownAPI(options); // To get here as well, you need to be sure the threads have finished.

I hope this clears some things up at least? And I'll get back to you on why the upload Handle is updated to FAILED twice sometimes.
Again, let me know if I misunderstood something or if you got other questions.


What URL is queried here?

I just noticed that this doesn't check a pypi URL but your own server: https://github.com/bboe/update_checker/blob/master/update_checker.py#L109-L112
What's the story for that, why not use pypi directly?

I use it to obtain information about package version, python version and os information for my packages.  This enables me to make data-driven decisions for my packages such as what versions of python I should continue to support.
You can replace the URL with your own instance of the update checker app if you prefer. https://github.com/bboe/update_checker_app

Ah, ok, I thought this was a generic script to check for pypi updates. Sorry for the noise....

Wouldn't be a bad idea to fork this repo and make a version that hits pypi
instead. @bboe has been very generous by adding some of my projects to his
supported projects list, but I imagine he doesn't want to extend that to
the world.
On Monday, March 7, 2016, Jan Schulz<EMAIL_ADDRESS>wrote:

Ah, ok, I thought this was a generic script to check for pypi updates.
Sorry for the noise....
—
Reply to this email directly or view it on GitHub
https://github.com/bboe/update_checker/issues/8#issuecomment-193395789.

--
Randal S. Olson, Ph.D.
Postdoctoral Researcher, Institute for Biomedical Informatics
University of Pennsylvania
E-mail<EMAIL_ADDRESS>| Twitter: @randal_olson
https://twitter.com/randal_olson
http://www.randalolson.com

It would certainly be reasonable to have a "default" version of this package that hits pypi directly instead of my server.

Or what about an enhancement to this package that pings your server to see if it's a supported package, and if not, checks PyPi?

If this is used as a general-purpose package I'd rather it not always hit my server, and only do that by default for projects that are explicitly allowed.
Until now no one aside from me has expressed any interest in the package.

We can build a whitelist into this package then:

Check if project being checked is in whitelist

If yes, hit your server

If no, hit pypi

It's quite a useful package! If we can make it general-purpose, I'm sure many other packages would adopt it.

I'd prefer to keep the whitelist out of this package. The default update_checker class should always hit pypi. By passing in an app_url (or similar) will have it (1) use that URL and (2) assume it's talking to an "update_checker" app.

Yeah, that sounds better, with a default to pypi. What's your bandwidth look like? I haven't looked at the code yet, so I don't know how big of a change this would be.

I've been working on the next major version of PRAW.  I'll save this work for someone who really wants to hit pypi directly as it's not terribly important to me at this time.
The code to hit pypi already exists in update_checker_app. In fact, we could probably move that portion to here, and have update_checker_app depend on update_checker to do that part.


Align dl.matmul with tf.matmul

Use booleans transposeA/B instead of the enum MatrixOrientation. Support the enum for backwards compatibility.
Fixes #697

This change is

Reviewed 10 of 11 files at r1, 1 of 1 files at r2.
Review status: all files reviewed at latest revision, 5 unresolved discussions.

src/engine_test.ts, line 219 at r2 (raw file):

    // de/da = dot(de/dy, bT)
    expect(da.shape).toEqual(a.shape);
    expectArraysClose(da, dl.matMul(dedm, b, false, true), 1e-1);

pull these out to variables or put comments :)

src/ops/matmul.ts, line 27 at r2 (raw file):

export class Ops {
  /**
   * Computes the dot product of two matrices, A * B. These must be matrices,

add a blank line after A * B

src/ops/matmul.ts, line 28 at r2 (raw file):

  /**
   * Computes the dot product of two matrices, A * B. These must be matrices,
   * use matrixTimesVector and vectorTimesMatrix, dotProduct, and outerProduct

use backticks to link to the other methods

src/ops/matmul.ts, line 29 at r2 (raw file):

   * Computes the dot product of two matrices, A * B. These must be matrices,
   * use matrixTimesVector and vectorTimesMatrix, dotProduct, and outerProduct
   * in other cases.

add a blank line after this jsdoc

src/ops/matmul_test.ts, line 38 at r2 (raw file):

    const b = dl.tensor2d([1, 0, 2, 4, 3, 0], [2, 3]);

    const c = dl.matMul(a, b, false, true);

comments / vars please :)

Comments from Reviewable


ros2 foxy error

ISSUE TEMPLATE ver. 0.4.0

Which TurtleBot3 platform do you use?

[x] Burger
[ ] Waffle
[ ] Waffle Pi

Which ROS is working with TurtleBot3?

[ ] ROS 1 Kinetic Kame
[ ] ROS 1 Melodic Morenia
[ ] ROS 1 Noetic Ninjemys
[ ] ROS 2 Dashing Diademata
[ ] ROS 2 Eloquent Elusor
[x] ROS 2 Foxy Fitzroy
[ ] etc (Please specify your ROS Version here)

Which SBC(Single Board Computer) is working on TurtleBot3?

[ ] Intel Joule 570x
[ ] Raspberry Pi 3B+
[ ] Raspberry Pi 4
[x] etc (Please specify your SBC here)

Which OS you installed on SBC?

[ ] Raspbian distributed by ROBOTIS
[ ] Ubuntu MATE (16.04/18.04/20.04)
[x] Ubuntu preinstalled server (18.04/20.04)
[ ] etc (Please specify your OS here)

Which OS you installed on Remote PC?

[ ] Ubuntu 16.04 LTS (Xenial Xerus)
[ ] Ubuntu 18.04 LTS (Bionic Beaver)
[x] Ubuntu 20.04 LTS (Focal Fossa)
[ ] Windows 10
[ ] MAC OS X (Specify version)
[ ] etc (Please specify your OS here)

Specify the software and firmware version(Can be found from Bringup messages)

Software version: [x.x.x]
Firmware version: [x.x.x]

Specify the commands or instructions to reproduce the issue.

HERE

Copy and Paste the error messages on terminal.

HERE

Please describe the issue in detail.

HERE

need help with the first error
was tryna simulate dqn using turtlebot3 in gazebo11 using os foxy encountered this error specifically.
ros2 run turtlebot3_drl gazebo_goals
running on stage: 4, dynamic goals enabled: False
Traceback (most recent call last):
File "/opt/ros/foxy/lib/python3.8/site-packages/rosidl_generator_py/import_type_support_impl.py", line 46, in import_type_support
return importlib.import_module(module_name, package=pkg_name)
File "/usr/lib/python3.8/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1014, in _gcd_import
File "", line 991, in _find_and_load
File "", line 973, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'turtlebot3_msgs.turtlebot3_msgs_s__rosidl_typesupport_c'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/ashwath/turtlebot3_drlnav/install/turtlebot3_drl/lib/turtlebot3_drl/gazebo_goals", line 11, in
load_entry_point('turtlebot3-drl', 'console_scripts', 'gazebo_goals')()
File "/home/ashwath/turtlebot3_drlnav/build/turtlebot3_drl/turtlebot3_drl/drl_gazebo/drl_gazebo.py", line 263, in main
drl_gazebo = DRLGazebo()
File "/home/ashwath/turtlebot3_drlnav/build/turtlebot3_drl/turtlebot3_drl/drl_gazebo/drl_gazebo.py", line 74, in init
self.task_succeed_server    = self.create_service(RingGoal, 'task_succeed', self.task_succeed_callback)
File "/opt/ros/foxy/lib/python3.8/site-packages/rclpy/node.py", line 1300, in create_service
check_for_type_support(srv_type)
File "/opt/ros/foxy/lib/python3.8/site-packages/rclpy/type_support.py", line 29, in check_for_type_support
msg_type.class.import_type_support()
File "/home/ashwath/turtlebot3_drlnav/install/turtlebot3_msgs/lib/python3.12/site-packages/turtlebot3_msgs/srv/_ring_goal.py", line 273, in import_type_support
module = import_type_support('turtlebot3_msgs')
File "/opt/ros/foxy/lib/python3.8/site-packages/rosidl_generator_py/import_type_support_impl.py", line 48, in import_type_support
raise UnsupportedTypeSupport(pkg_name)
rosidl_generator_py.import_type_support_impl.UnsupportedTypeSupport: Could not import 'rosidl_typesupport_c' for package 'turtlebot3_msgs'

Hi @Ashwath12052004
Thank you for sharing the details of the issue. It seems that the turtlebot3_msgs package's type support (rosidl_typesupport_c) might be missing.
Please try installing the turtlebot3_msgs package by running the following command:
sudo apt install ros-foxy-turtlebot3-msgs

After reinstalling, try running your program again to see if the issue is resolved.
Let us know if you continue to encounter problems.

@Ashwath12052004 Apologies for the delayed response. We have assembled a TF team to address TurtleBot3 issues and are actively working on resolutions. Please note that we do not support EOL (End-of-Life) ROS versions; our support currently extends to Noetic and Humble versions. We kindly ask that you try again with the latest version. If the same issue arises, please feel free to resubmit it, and we will address it promptly.


Link not working in [Part 3, Module 01, Exercise 4]

Describe the bug
A link is not working in [Part 3, Module 01, Exercise 4], and thus, giving a 404 response code. The links are Calling different kinds of methods in the .NET Class Library.
To Reproduce
Steps to reproduce the behavior:

Go to this link
Check all the links in this markdown, or directly open the links provided in the "Describe the Bug" section.

Expected behavior
The links should work, and must not give a 404 error.
Screenshots

🎓 Student Ambassador

Yes I noticed this problem as well

@anshgoyalevil Sorry - this is an internal link to an internal private repo topic that gets processed through the build system.
any link starting with 'https://github.com/MicrosoftDocs/learn-pr/blob' is OK and will resolve when published

Closing since this will be resolved when published


XML version issue

I am able to install this successfully in on-prem, but when installing in Splunk cloud im able to see multiple errors attached below.

Failures will block the Cloud Vetting. They must be fixed.
check_that_extracted_splunk_app_does_not_contain_prohibited_directories_or_files
A prohibited file or directory was found in the extracted Splunk App: .gitignore

check_that_splunk_app_package_does_not_contain_files_outside_of_app
A file or folder was found outside of the app within the overall package. OR the file or folder does not have expected permission. Please remove this file or folder OR modify the permission : SA-cim_vladiator-1.8.0

check_simplexml_standards_version
Change the version attribute in the root node of your Simple XML dashboard default/data/ui/views/cim_dictionary.xml to `<version=1.1>`. Earlier dashboard versions introduce security vulnerabilities into your apps and are not permitted in Splunk Cloud File: default/data/ui/views/cim_dictionary.xml

Change the version attribute in the root node of your Simple XML dashboard default/data/ui/views/cim_validator.xml to `<version=1.1>`. Earlier dashboard versions introduce security vulnerabilities into your apps and are not permitted in Splunk Cloud File: default/data/ui/views/cim_validator.xml

just an FYI  i am on :-
Splunk Cloud Version:    8.2.2112 (Victoria)

Adding  to "cim_dictionary" and "cim_validator" files fixed the issue for me.

yes that's the fix, hopefully someone will update it here.

I also had to do these 2 lines fix to be able to deploy in SplunkCloud via private app


Fix onready vars / vars accessing class members if _ready / _init not present

Fixes #19548
Please review
I'm assuming that the condition was supposed to check for a static function only as per http://docs.godotengine.org/en/3.0/getting_started/scripting/gdscript/gdscript_basics.html:
"When a function is static it has no access to the instance member variables"

Could you amend the commit log to be more explicit (git commit --amend)? A commit log should explain what the commit does in a human-readable way, independently of the issue tracker (in git log you don't have the data from GitHub), see https://github.com/godotengine/godot/blob/master/CONTRIBUTING.md#format-your-commit-logs-with-readability-in-mind for details.

I don't think this is the right fix. I was investigating this right now and the problem is that the _static field is never set if it does not have an actual function in the code (i.e. it's generated by the compiler).

I'm not sure how setting _static = false helps here as the function_node is still NULL if _ready func is missing.

@dragmz true. Now I realize that both changes are needed. Because currently it's filling the _static field with garbage because it's never set (and the rpc_mode too).
But this PR is okay. The null check is not important because it's not accessed later.

Now that Godot 3.1 has been released, we only plan to cherry-pick critical bug fixes to the 3.0 branch, unless there is very strong support in favor of a specific non-critical issue. Removing cherrypick label for 3.0.


x/sys/windows/svc/eventlog.Open() fails with "Access Denied" on older versions of Windows Server, when compiled with latest Go v1.17.1

What version of Go are you using (go version)?

$ go version - 1.17.1

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env

Built on Windows Server 2016, VS2017, AMD64
Problems observed on Windows Server 2008R2 and Windows Server 2012R2, AMD64
What did you do?
Call to x/sys/windows/svc/eventlog.Open() returns "Access is denied"
What did you expect to see?
Service is running at elevated privileges, should open without error
What did you see instead?
On Windows Server 2008R2 and Windows Server 2012R2, calls to open eventlog fails with "Access" is denied.
This problem is not seen on newer versions of Windows Server (2016, 2019)
Problem is also not seen when compiled using Go 1.16.4. The program was running well, until upgrade to Go v1.17.1.

To clarify, this problem happens only with Go 1.17.1? Not with Go1.17?

I tested with Go 1.17.0, and same failures are seen.

@alexbrainman @bradfitz

Can you post a stand-alone example program that illustrates the problem? This would make it a lot easier to work on.

"Access is denied"

This error can be returned for many different reasons.
It is impossible to help here without at least a repro.
Alex

I will try to create a small repro program, but that might take me a while, since I don't have a Windows machine.
I can only speculate here, but is there any difference in how event log is opened in older versions of Windows vs. newer versions? I read that Go v1.17 introduced some changes to syscalls. Could that make a difference?

I have been unable to repro this.  Will close this for now.


Automation support for POC team

Issues under this epic are tracking needs from the POC automation team to enable their use of the SE standard tools.

I believe this was built out of the testing of Epics and we deemed we weren't going to use those.  Closing


Rails 4.1.1 development class reloading issue

We are trying to integrate Forem into a Rails4.1.1 app but so far we're running into issues with the reloading of the Forem classes in development.  For example,
1st request is OK -- we can see the forem page.
2nd request we'd get an error like
NameError in Forem::Categories#show
Showing /Users/alex/.rvm/gems/ruby-2.0.0-p247/bundler/gems/forem-c793fb195ad4/app/views/forem/forums/_forum.html.erb where line #7 raised:
uninitialized constant Forem::Forum::Post
Disabling the cache reloading in config/environments/development.rb (config.cache_classes = true) fixes the issue since now the classes don't get reloaded.
We're using Forem off the rails4 branch already:
gem 'forem', :github => "radar/forem", :branch => "rails4"

+1
we got same things

Please show me your Gemfile.

+1
Same issue here.  For me, every time it's uninitialized constant Forem::StateWorkflow.  I have to restart my server almost every time I make a change.  Development is extremely painful now.
Gemfile:  https://gist.github.com/cjbottaro/4373517f4a8efcb6e3e1

Any particular reason why you're stuck on 4.1.1 and can't upgrade to 4.2.4?

I'm not sure what you mean.  The Gemfile that I posted shows 4.2.4.  In fact, I had to upgrade to 4.2.4 (from 4.2.3) just to get it to work (due to dependencies specified in the gemspec).

You're commenting on an issue that says it has a problem with 4.1.1. You said you have the same issue.
I didn't see that your Gemfile contained 4.2.4.

On 31 Aug 2015, at 11:04, Christopher J. Bottaro<EMAIL_ADDRESS>wrote:
I'm not sure what you mean. The Gemfile that I posted shows 4.2.4. In fact, I had to upgrade to 4.2.4 (from 4.2.3) just to get it to work (due to dependencies specified in the gemspec).
—
Reply to this email directly or view it on GitHub.

Whoops, sorry about that.  I meant to say I'm also experiencing this with Rails 4.2.4.

Could someone please share with me a basic application which reproduces this issue? I'm having a hard time reproducing it myself.

This is fixed now by #679.


Apps always only start on the primary display

When you start an app from the IDE, it always shows on the primary display on Windows 10. There's no way that I can see to make it start on the same display as the IDE is on (I usually keep the IDE on the secondary display)

Would add to this, there seems to be no way to choose which display a window or dialog is shown on. If you open a dialog or window, it always opens on the main display, even if the app is on another display (and the user focus also is), which is not great UX.

Thanks for looking into it @igordmn 🙌

In https://github.com/JetBrains/compose-jb/issues/1845 we show the new window on the same display, where the previous window was. But we still show the very first window on the default display, because we can't know the display of the previous process (IDEA in our case). At least I don't know how we can implement that.
I plan to extend API for manual display choosing (not in 1.2.0). Then you will be able to add something like -Pdisplay=2 in your run configuration.

That sounds like a perfectly valid solution for the problem 👍

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Updated installation process.

This pull request updates the installation process and fixes issues with the setup.py script. The setup.py script can now be used in either install mode or in develop mode.
Changes include: Removed extraneous files. Revised setup.py. Updated README.md. Modified scripts for the the Docker image to reflect the correct version labeling per the SAS User Guide.
Before approving this Pull Request, please test to ensure that this works:

Create a new (clean) conda environment
Follow all of the instructions in the README.md (including creating a new clone of the repo) to make sure that it works.
Please also check that the Docker Image can still be built and run from the command line, per the SAS User Guide.

Thank you!

Thank you, @hfattahi !

Thank you @hfattahi !


Connection timeouts (unable to connect)

I'm using the VS Code Desktop button and am unable to connect:
Remote - SSH Output:
[08:55:24.525] Log Level: 2
[08:55:24.584] VS Code version: 1.77.3
[08:55:24.584] Remote-SSH version<EMAIL_ADDRESS>[08:55:24.584] darwin x64
[08:55:26.019] SSH Resolver called for "ssh-remote+coder-vscode--bpmct--dev", attempt 1
[08:55:26.019] "remote.SSH.useLocalServer": false
[08:55:26.020] "remote.SSH.showLoginTerminal": false
[08:55:26.020] "remote.SSH.remotePlatform": {"coder-vscode--bpmct--ben-stable":"linux","coder-vscode--bpmct--websites":"linux","coder-vscode--bpmct--backstage":"linux","coder-vscode--bpmct--vnc":"linux","coder-vscode--ben--my-workspace":"linux","coder-vscode--bpmct--projects":"linux","coder-vscode--ben--testing-permissions":"linux","coder-vscode--bpmct--hello1":"linux","coder-vscode--bpmct--workshop2":"linux","coder-vscode--bpmct--workshop":"linux","coder-vscode--bpmct--systemd-workshop":"linux","coder-vscode--bpmct--ben":"linux","coder-vscode--ben--test":"linux","coder-vscode--bpmct--dev":"linux","coder-vscode--bpmct--android":"linux","coder-vscode--bpmct--avd2":"linux","coder-vscode--ben--yipee":"linux","coder-vscode--ben--dev":"linux","coder-vscode--BrunoQuaresma--bruno-br":"linux"}
[08:55:26.020] "remote.SSH.path": undefined
[08:55:26.020] "remote.SSH.configFile": undefined
[08:55:26.020] "remote.SSH.useFlock": true
[08:55:26.021] "remote.SSH.lockfilesInTmp": false
[08:55:26.021] "remote.SSH.localServerDownload": auto
[08:55:26.021] "remote.SSH.remoteServerListenOnSocket": false
[08:55:26.021] "remote.SSH.showLoginTerminal": false
[08:55:26.021] "remote.SSH.defaultExtensions": []
[08:55:26.022] "remote.SSH.loglevel": 2
[08:55:26.022] "remote.SSH.enableDynamicForwarding": true
[08:55:26.022] "remote.SSH.enableRemoteCommand": false
[08:55:26.022] "remote.SSH.serverPickPortsFromRange": {}
[08:55:26.022] "remote.SSH.serverInstallPath": {}
[08:55:26.041] SSH Resolver called for host: coder-vscode--bpmct--dev
[08:55:26.041] Setting up SSH remote "coder-vscode--bpmct--dev"
[08:55:26.044] Using commit id "704ed70d4fd1c6bd6342c436f1ede30d1cff4710" and quality "stable" for server
[08:55:26.048] Install and start server if needed
[08:55:26.059] PATH: /usr/local/opt/openjdk/bin:/Users/benpotter/.gem/ruby/3.2.1/bin:/Users/benpotter/.rubies/ruby-3.2.1/lib/ruby/gems/3.2.0/bin:/Users/benpotter/.rubies/ruby-3.2.1/bin:/Users/benpotter/.deno/bin:/Users/benpotter/.nvm/versions/node/v14.19.3/bin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/go/bin:/Library/Apple/usr/bin:/usr/local/bin:/Applications/Visual Studio Code.app/Contents/Resources/app/bin:/usr/local/sbin/:/Users/benpotter/go/binATH=/Users/benpotter/.gem/ruby/3.2.1/bin:/Users/benpotter/.rubies/ruby-3.2.1/lib/ruby/gems/3.2.0/bin:/Users/benpotter/.rubies/ruby-3.2.1/bin:/Users/benpotter/.deno/bin:/Users/benpotter/.nvm/versions/node/v14.19.3/bin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/go/bin:/Library/Apple/usr/bin:/usr/local/bin:/Applications/Visual Studio Code.app/Contents/Resources/app/bin:/usr/local/sbin/:/Users/benpotter/go/bin:/Users/benpotter/Library/Android/sdk/emulator:/Users/benpotter/Library/Android/sdk/tools:/Users/benpotter/Library/Android/sdk/platform-tools
[08:55:26.060] Checking ssh with "ssh -V"
[08:55:26.066] > OpenSSH_9.0p1, LibreSSL 3.3.6

[08:55:26.071] Running script with connection command: ssh -T -D 56731 -o ConnectTimeout=15 'coder-vscode--bpmct--dev' bash
[08:55:43.074] Resolver error: Error: Connecting with SSH timed out
	at m.Timeout (/Users/benpotter/.vscode/extensions/ms-vscode-remote.remote-ssh-0.100.0/out/extension.js:1:584271)
	at Timeout._onTimeout (/Users/benpotter/.vscode/extensions/ms-vscode-remote.remote-ssh-0.100.0/out/extension.js:1:680275)
	at listOnTimeout (node:internal/timers:559:17)
	at process.processTimers (node:internal/timers:502:7)
[08:55:43.087] ------

Extension output:
Found existing binary: /Users/benpotter/Library/Application Support/Code/User/globalStorage/coder.coder-remote/bin/coder-darwin-amd64
Using binName: coder-darwin-amd64
Using binPath: /Users/benpotter/Library/Application Support/Code/User/globalStorage/coder.coder-remote/bin/coder-darwin-amd64
Using ETag: 3b7a1d5aa822eb617912fc8ac3edacc25d263884
Response status code: 304
Using cached binary: /Users/benpotter/Library/Application Support/Code/User/globalStorage/coder.coder-remote/bin/coder-darwin-amd64

I tried restarting my workspace. Sadly, still unable to connect.


Refer entities by foreign key id, instead of foreign key values in the published json

All references to parent entities use values now in the published json. These should be replaced by their ids.

Fixed by merge #63


Add cycle.js to DefinitelyTyped

A low priority feature request.
Add cycle.js (and other cycle.js-related projects) to https://github.com/DefinitelyTyped/DefinitelyTyped (the home page for the project is http://definitelytyped.org).
Some tools (notably, IntelliJ IDEA) support these definitions to provide better code insights.

Hi, thank you for taking your time to send us this issue. We appreciate it, however we are already in the process of rewriting Cycle entirely in TypeScript, which will fulfill this need. So that's why I'll close this issue.

Hi, This might not be the best place to say this, but I'm a big fan of Cycle and would love to be able to use it with Typescript ASAP and therefore I'd also love to contribute to . Now I've checked out the Typescript branch, but the latest commit was from June 2015. Am I missing something? Where do I start? Would appreciate any help!

Check #196 for the overall progress in this direction. If you want to help, clone the cycle-dom repo, checkout the diversity branch, then try to make one more test pass, then submit a PR. One PR per test. I myself will be doing this next week too. The typescript branch is old, deprecated.

Awesome! I'll see if I can help!

@staltz What is your advice for people picking up cycle today, who want to use typescript? Wait for the upcoming typescript version? Set aside typescript and use cycle with plain ES6? ES5?

Use ES6 today. It won't be too hard to convert ES6=>TS.

Thanks. I just got an example project up and running with Cycle, ES2015, and Rollup. But I miss TypeScript already...

@staltz Just finally got around to running those tests, but it seems you're already done? Next step would be HTTP?

Yes

@kylecordes if you are feeling brave, you could try this starter project that uses TypeScript with the current Cycle.js https://github.com/eldarlabs/cycle-ui-typescript-webpack, or just pick bits from it to add to your own project.

I had not seen that starter project, but I have thought about this picking up the current cycle with typescript. But I put together these bits:

@staltz has a strong appreciation of typescript.
He is working on a new version of cycle, and typescript.
He appears to be a rather productive developer.
It seems to be taking some time.

Taking that information jointly, I conclude that the new cycle will be considerably different than just taking the current cycle and applying types around it. Presumably if the plan were to rename the files .ts, adjust the imports for typescript syntax and idiosyncrasies, and ship, then it would be done by now. Therefore I assume that the shape of Cycle and its is changing somewhat, and that I probably don't want to dig into the pre-typescript version much.

Taking that information jointly, I conclude that the new cycle will be considerably different than just taking the current cycle and applying types around it. Presumably if the plan were to rename the files .ts, adjust the imports for typescript syntax and idiosyncrasies, and ship, then it would be done by now. Therefore I assume that the shape of Cycle and its is changing somewhat, and that I probably don't want to dig into the pre-typescript version much.

For users of Cycle.js, the new version will be mostly backwards compatible, so don't be afraid of using the current online version.

@staltz as a proponent of TS, I was wondering what was your biggest motivating factors for migration to TS for cyclesjs?

http://staltz.com/all-js-libraries-should-be-authored-in-typescript.html

ah good points!


Tables cut off in pdf

When I create the pdf some of the tables within it are cut off, here is an example
https://jsfiddle.net/RyMac44/tz64sahr/2/

I'm somewhat running into the same problem except my tables are too wide, so they're cut off on the sides.

@harryadel add margins to the table using CSS


States incorrect support for Trusty

The meta information says this role supports Ubuntu 14.04 LTS, Trusty.  However, the task assumes systemd, and it wasn't until 15.04 that systemd replaced upstart in Ubuntu.

thanks for pointing that out. i should have adjusted the meta data after I tied the config to systemd. I just published a new version v1.0.2 that corrects the metadata. trusty is long in the tooth. looking forward to xenial!


fix: update type to indicate that route ID may be null

We've hit this a couple times recently on svelte.dev. Hopefully better types will prevent us from making the same mistake

Where did that happen to be wrong? RouteId is a generic parameter which is string|null by default.
We should be very careful here as this could be seen as a breaking change if this affects more than we want it to

Ah, I missed that RouteId itself could be null. Thanks for catching that. Let me check why we're not catching the potential error in svelte.dev


[FEATURE] Add a feature for admin approval for blogs.

Is your feature request related to a problem? Please describe.
The blogs that are uploaded in the website could be at risk of being polluted with content not fit for public. So for that reason, we want the blogs to be approved by the admin before being displayed for public at /blogs page.
Describe the solution you'd like!
The solution is to introduce a feature to approve blogs by the admin before being available for general audience. The solution may include:

Introducing a new Boolean field in blogs model 'approved' with default as False.
Only allowing users to see blogs that are approved by admin.
At /adminportal, make a table "Blogs to be approved" under dashboard for admin consisting to blogs awaiting approval.
Add two buttons in the table, "Approve" and "Discard". "Approve" will change the value of approved field in blogs model to True and "Discard" will delete that blog.
Make sure the table you make is responsive.

Describe alternatives you've considered
Feel free to suggest!
Developer Help
None.

@SamakshAgarwal1112 i would like to work on this issue. I would modify the blog model in applications/blog/models.py and add the necessary field. also i would make a responsive table UI in /adminportal where the blogs can be approved or discarded by the admin only.

@rohansen856 Go ahead


registry

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/69872
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.0.1 -m "<description of version>" 57ca31bb5569ff49df23998475475f1cfe721835
git push origin v0.0.1

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/70148
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.0.2 -m "<description of version>" 7b19e9caed336b60f0a551e563f186159e57e72a
git push origin v0.0.2

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/70730
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" ea9bffa2b121ffe5a8015f3ecd81fdc8bfe54e04
git push origin v0.1.0


Bring back ability to load new patterns

:test

My last commit added a combobox for adding patterns just for the sake of debugging.
To be feature parity, you should also be able to delete patterns.


Illustrating history and technology with visuals

What does this PR do?
Isssue #158

added visuals across 2-1 to 4-3

@GlenWeyl @nishio kindly review how image tags are structured

Thanks🚀! I am happy to make needed changes and add more content, but I would suggest not closing the issue

I agree.  As mentioned, Audrey may not retain all the art you added, but I am glad you added it.

Research Lead, Plural Technology Collaboratoryhttps://aka.ms/plural, Research Special Projects

Collaboratehttps://github.com/pluralitybook/plurality with Digital Minister Audrey Tang, myself and dozens around the world to tell the story of Pluralityhttps://www.plurality.net/

From: Guy Ntare @.>
Sent: Thursday, March 21, 2024 12:03 AM
To: pluralitybook/plurality @.>
Cc: Glen Weyl @.>; State change @.>
Subject: Re: [pluralitybook/plurality] Illustrating history and technology with visuals (PR #719)
Thanks🚀! I am happy to make needed changes and add more content, but I would suggest not closing the issue
—
Reply to this email directly, view it on GitHubhttps://github.com/pluralitybook/plurality/pull/719#issuecomment-2011178527, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABIRKSE3HCRBGVQL2S42EU3YZJLZRAVCNFSM6AAAAABE6YFXQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJRGE3TQNJSG4.
You are receiving this because you modified the open/close state.Message ID: @.***>


KAFKA-10893 Increase target_messages_per_sec of ReplicaScaleTest to r…

issue: https://issues.apache.org/jira/browse/KAFKA-10893
The expected size is 3400000 and the throttle is 10000 msg/sec so the expected minimal run time of one consumer/producer is about 6 mins. Hence, the test case is always timeout on travis (6 + 6 > 10 mins)
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@mumrah Thanks for your reviews. Merge it to trunk

@mumrah Thanks for your reviews. Merge it to trunk


update UpdateVisuals to use Destructible thresholds

About the PR
Addresses #2959.
It changes it so that window's visual cracking rely on the Destructible component's first destruction threshold

Okay, the changes have been made. I had a feeling that that was what I was supposed to do initially, but I just wanted to make sure.

Okay, the changes have been made. I had a feeling that that was what I was supposed to do initially, but I just wanted to make sure.

It appears that there already is a Destructible component added to the prototypes with the correct maxDamage values.

This is the case for every window that is defined in the windows.yml file
Is there somewhere else that I need to edit it as well?

It appears that there already is a Destructible component added to the prototypes with the correct maxDamage values.

This is the case for every window that is defined in the windows.yml file
Is there somewhere else that I need to edit it as well?


PyCon Uruguay 2013

PyCon UY 2013

Playlist
https://www.youtube.com/watch?v=GzorUnKdwb4&list=PLfvJ0GULhS69Ir4As8Vd5wrqRbOZKgIX8

Schedule can be found at https://web.archive.org/web/20131103102200/http://uy.pycon.org/es/schedule


fix(Toast): check if window exists to run startTimer in CSR only

fix issue #1246

Thanks for the issue and PR @rankjie !! Nicely done!


Update Consul API support to 1.2.0

Consul 1.0.7 was the last version to support the string Script API, which had been long deprecated. 1.1.0 and later use []string Args. This PR updates Consul support to this new property, bumps the Consul version to 1.2, and the Alpine version to 3.8.
Various docker/ dependencies are updated as well. The fsouza/go-dockerclient dependency is pinned to 1.2.2 for this change to work.

Hi @josegonzalez, can you please take a look at this PR and merge it if you accept the changes? It fixes a couple open issues.

Also a nudge @dsouzajude @mattatcha @progrium to see if we can get this merged. Thanks in advance!

We meet with the same problem.
Guys :) Would be nice to resolve this MR :) @josegonzalez @dsouzajude @mattatcha @progrium

@timiTao We'll get to it when we get to it. There isn't any need to ping anyone to do that. Thanks.

yeah I gave up and wrote my own version. sigh
https://github.com/hampsterx/ecs-consul-reg
you probably don't want to use it but works for us (using aws ECS). pretty simple..

@josegonzalez We're assuming you won't support this and have begun investigating an alternative solution that may take another 6-8 months to implement.
Some clarification from your side would help us plan such a long-term alternative. Thank you and appreciate everything you all have done.

I've come up with a similar fix in #669 before noticing this PR - would be good to get one of these merged, as the current tree simply fails to build for me otherwise.

+1

Hi @josegonzalez
I have upgraded to consol 1.6.1 and started noticing errors in registrator to do with SERVICE_443_CHECK_SCRIPT like  :
Unexpected response code: 400 (Invalid check: TTL must be > 0 for TTL checks)
My services are not being registered as expected.
I tried upgrading Registrator by deploying the latest docker image from master branch but am still seeing the above error.
after pulling down the branch for this PR and compiling the Registrator container and deploying it I can now see the services being successfully registered in consul and I'm able to browse the endpoints :
2019/11/19 04:34:51 added: xxxxxxxxxxxx xxxxxxxxxxx:xxxxxxxxx:443

Would you be able to review this PR and if you have no further objections approve and merge it into the master branch?
I think there are quite a few people experiencing this issue, so it would be nice to have this PR merged.
Registrator is a great application, let's keep the dream alive!

@nicofuccella this is your baby, have fun! :D

@nicofuccella this is your baby, have fun! :D

I just merged in another PR without conflicts that handles this :)

hi @mattatcha I pulled latest master Registrator container this morning and deployed, I'm seeing the following error in Consul in the Health Checks tab :
fork/exec curl --silent --fail http://xxxxxxxxx:xxxxxxxx/xxxxxxx/HealthCheckService: no such file or directory

I'm setting the healthcheck on our web server container via environment env :
"SERVICE_4443_CHECK_SCRIPT=curl --silent --fail http://xxxxxxxxxx:xxxxxxx/xxxxxxxxx/HealthCheckService",

If I revert the Registrator container back to the one compiled from this PR branch the health checks go green again and I'm able to browse the endpoint.

@alaverty would you be able to create a PR with the correct changes to consul/consul.go?

@mattatcha I have branched from master and made the required changes to consul/consul.go
the PR is GH-670
I've compiled this PR branch and deployed it and can confirm the healthchecks are working as expected and healthy in consul.


More details on -L option

Hi,
Quick question: what does it imply to use the -L option ? Long reads have multiple differences between datasets so I would like to know how to adapt this option. More precisely, could we reproduce the -L option by a combination of all the other options (eg -j, -m, -g...) ?
Thanks

To answer your latter question: no, -L cannot be simply reproduced by a combination of other parameters. When -L option is provided there is actually a different branch of code running there (specialized bundle processing functions), with its own specific assumptions about the alignment characteristics, the higher error rate etc. (@mpertea may add to this basic answer if needed, as she is the main author who implemented the core algorithms in StringTie including the novel -L code).

Thanks @gpertea for your reply. As I'm comparing the output of novel annotations made from long reads and shorts reads, that would be lovely to get more details from @mpertea if possible. Also, do you know if PacBio and Nanopore data are handled the same way with the -L option ?


24 mwmealcleaner

added a cleaner for the Meals that takes the Meals from the Parser and changes them according to the desired standards. Happy about feedback on names and things I missed

i have now implemented the floats to always have two decimals after the dot

I totally see that, i'd like someone else's feedback regarding this topic. If there is another opinion against the Price object I will use the JSON


no edge support anymore

please remove edge 'implementation'/support from the docs.
it's not working anymore, and the issue is known for some time:
https://github.com/Microsoft/edge-diagnostics-adapter/issues/59
and it will never get fixed again:
https://github.com/Microsoft/edge-diagnostics-adapter/issues/59#issuecomment-343245521

Oh, thanks for the heads up.

and it will never get fixed again:

Well hopefully there will be no more need for an adapter in the future.


Support letter format

One of the commenters at HN asked about support the letter format as well. I will have to look into this because I am not sure how KOMAscript likes it.

Thanks to KOMAscript, the fix is quite easy: it is sufficient to add \KOMAoptions{paper=letter} to the preamble of the document. Documenting this now before closing the issue.


[NEW ALGORITHM] Gift Wrapping Algorithm

Issue will be closed if:

You mention more than one algorithm. You can create a separate issue for each algorithm once the current one is completed.
You propose an algorithm that is already present or has been mentioned in a previous issue.
You create a new issue without completing your previous issue.

Note: These actions will be taken seriously. Failure to follow the guidelines may result in the immediate closure of your issue.

Name:
[NEW ALGORITHM] Gift Wrapping Algorithm
About:
Propose a new algorithm to be added to the repository
Because its a straightforward algorithm used to find the convex hull of a set of points in a two-dimensional plane.
Labels:
new algorithm, gssoc-ext, hacktoberfest, level1

Assignees:

[X] Contributor in GSSoC-ext
[X] Want to work on it

/assignme


Add KTO

PR types

PR changes

Description

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: w5688414:white_check_mark: ZeyuChen:x: 吴高升吴高升 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Support >1.0 for OpenAI integration/package

Open Source Contributors Welcomed!
Please comment below if you would like to work on this issue!
Contact Details [Optional]
<EMAIL_ADDRESS>What happened?
The current openai integration in ZenML is pinned to versions below 1.0.0. However, OpenAI has recently released a significant update (version 1.0.0 and above), which includes major changes. To stay up-to-date and take advantage of the new features and improvements, ZenML needs to support the latest OpenAI versions. This update might necessitate a breaking change in ZenML, shifting to support only versions >1.0.0 of the OpenAI integration.
Task Description
Update the openai integration within ZenML to support versions >=1.0.0. This task involves:

Unpinning the current version restriction in src/zenml/integrations/openai/init.py.
Ensuring compatibility with the new OpenAI version 1.0.0 and above.
Making necessary adjustments or rewrites in the ZenML codebase to accommodate any breaking changes introduced in the new OpenAI version.
Updating documentation and examples to reflect the new integration version support.
Considering making this update a breaking change for ZenML, where only OpenAI versions >1.0.0 will be supported going forward.

Expected Outcome
Successful integration of OpenAI version 1.0.0 and above in ZenML, with all tests passing and documentation updated to guide users on the new integration version.
Additional context
This update is crucial to keep ZenML integrations current and to provide users with the latest features and improvements from OpenAI.
Code of Conduct

[ ] I agree to follow this project's Code of Conduct

Hi @strickvl, should I work on this issue

@Senthi1Kumar if you'd like to! Please make sure to follow our contributors guide, esp by branching off and making your PR to the develop branch. Let us know if you have further questions or if you'd like to discuss your approach etc.

Having ridiculous trouble getting this to work with all the dependencies resolved... when i run
zenml integration install -y -i feast

or
pip install docs/.requirements-docs-frozen.txt

using the Docker container for zenml-dev.Dockerfile
the dependencies become impossible to resolve

Actually, now that I took a closer look, this ticket is blocked until we upgrade our Pydantic dependency to >2.0.0, since OpenAI pin this to v2.4.2. We're starting to work on this internally, but I'd hold off on this for the moment as it's currently impossible.

Okay no worries. Thanks for giving me the heads up :)


fix: set the correct database id on the key parent when calling Key#getParent

Fixes #1456 ☕
This is to fix the bug where the database ID is not set correctly on the parent key. The bug causes problems in Objectify by preventing you from fetching an entity from a non-default database, using a parent key.

Thank you so much for the fix and tests!

/gcbrun


Timestamps default value

Version information

Laravel: v5.7
Voyager: v1.1.10
PHP: 7.x
Database: mysql 5.7

Description
If you add timestamps which should be "not null", I can't add default value CURRENT_TIMESTAMP
Steps To Reproduce
Steps to reproduce the behavior:
Create a new table, and then add new field time timestamps, with "not null" option. Appear an error if you try to save without default value.
Expected behavior
I should be able to browse new model created.
I should be able to set default value to Current timestamp

@fletch3555 done

I can't reopen...

Please add a screenshot showing what you're trying to do and how

If I try to add 10,8 , when I click outside input then is automatically set to 10
If I try (10,8) then is saved as 10,0

That's unrelated since this issue was originally for timestamps.

Sorry, my mistake.
This is for timestamp, where you see that I check "Not null".

And this is error that you get if you try to save:

As default value for timestamps CURRENT_TIMESTAMP not work


Feature/todo list

I created a tasks list for every day in dayview by clicking on the button create task you can add task to the daily tasks list.
by clicking on the button todo list you can see all your daily tasks sorted by time and marked by important or not.
after you finish a task you can mark the task Done.

Codecov Report

Merging #285 (8891aca) into develop (8cd3a6e) will decrease coverage by 0.04%.
The diff coverage is 97.59%.

@@             Coverage Diff             @@
##           develop     #285      +/-   ##
===========================================
- Coverage    99.04%   98.99%   -0.05%
===========================================
  Files           52       54       +2
  Lines         2409     2491      +82
===========================================
+ Hits          2386     2466      +80
- Misses          23       25       +2

Impacted Files
Coverage Δ

app/main.py
96.66% <ø> (ø)

app/routers/todo_list.py
96.29% <96.29%> (ø)

app/database/models.py
96.55% <100.00%> (+0.25%)
:arrow_up:

app/internal/todo_list.py
100.00% <100.00%> (ø)

app/routers/dayview.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Refactors AVM1 object initialization and DoInitAction.

It's moving AVM1 script binding logic into _constructChildren(). The AVM1 specific methods were moved from AVM1MovieClip has to be moved (currently to the MovieClip) since during binding, and even before scripts are executed, AVM1 objects shall not exist.

/botio test

bad solution


Flaky tests that pass during retries mark PR as failed

I have retries set up and for whatever reason a test or two usually is flaky when run in CI. With 2 retries enabled, the test usually passes on one of the retries but is marked as flaky, which is fine. What isn't fine is that the PR shows the following:

which in turn marks the whole PR as failed:

I understand that a flaky test may or may not fail here and there, but it shouldn't mark the whole thing as failed, because the test is flaky and technically passing. For what its worth, that same test is not flaky when run in local through the Cypress app, but all things considered, it DID pass in CI after a retry so it shouldn't be showing up as a failed run for flakyness unless all retries also failed.
what's even more confusing is that in Cypress dashboard, the run shows up as passed (as it should).

the last run with the green circle and white check of this screenshot is the same run as the PR screenshots from up above.
This tends to be confusing because if Cypress dashboard marks the run as passed, so should the PR, no?

@reintroducing  The expected behavior is any reports of flake will result in a failed GitHub status check.
Here are a couple of options to prevent this:

Turn off the Report flaky tests option in the Project settings in the Cypress Dashboard

Remove the GitHub check for cypress/flake that is currently marked as required to not required

@conversaShawn I can confirm that turning off the Report flaky tests option "fixed" this, thank you.

It would be nice if I can configure this in GitHub Action parameter. Even if it's not required, all the pull requests will get the failure icon in the PR list. This makes it harder to find which PR is actually failing.


fix(material/tooltip): avoid problem when triggers hide animation for not visible tooltip

This PR fixes the problem when mat-tooltip-hide triggers the animation of tooltip that has not been shown yet.
Fixes #24614

A couple of notes:

I think that the correct approach would be to clear the tooltip opening timeout if the pointer is moved away.
I noticed this when I was reworking the tooltip in a5ab8e9, but I ended up keeping the old behavior, because it caused a lot of screenshot failures internally.

The problem is that during the hide action mat-tooltip-hide class is added which has @keyframes -> opacity: 1; animation. As a result hint is shown and disappears in the end of animation, but it hasn't be shown at all. In case when tooltip shouldn't be shown we need to avoid such animation.
After mouseleave event open timeout wipes.

Any update on this?

Hello @volvachev, we're running this PR through Google's internal presubmit. Could you please rebase this branch with master?

Hello @volvachev, we're running this PR through Google's internal presubmit. Could you please rebase this branch with master?

Hi, I did it.

tyty, the most recent presubmit process from earlier this week had less than ten failures. I'm kicking off a fresh one.

tyty, the most recent presubmit process from earlier this week had less than ten failures. I'm kicking off a fresh one.

So, will my fix be included in new one?

Any updates?

@volvachev The presubmit process Zach was describing was for this PR. Each PR is processed independently
From the latest presubmit run, I can see that it only had a handful of failures so it (hopefully) shouldn't be too difficult to get through.  It looks like there are no failed checks anymore. Is there any update on this PR?

Any news about this PR? The impacts of this bug are quite unpleasant for the users.

are we there yet?

Pretty please? 🙏

I'll take another look. We got this down pretty close but the internal failures are tough to debug. After rerunning internal tests tonight I'll post an update on how things are looking


SMSOTPMFA - Be able to change labels in the web console like other login texts

Preflight Checklist

[X] I could not find a solution in the existing issues, docs, nor discussions
[X] I have joined the ZITADEL chat

Describe your problem
According to this PR https://github.com/zitadel/zitadel/pull/7946.
It seems impossible to modify labels from the web console.
Describe your ideal solution
To implement the feature as other login texts.
Version
2.54.1
Environment
Self-hosted
Additional Context
No response

Thank you for sharing your idea.
If there is a significant demand from customers/community, we will carefully consider implementing the feature.
Currently, the issue will be added to our product backlog to collect feedback.
Meanwhile, if you're interested in implementing it yourself, we also welcome pull requests.


getSusiUrl should allow defaults

getSusiUrl should NOT require scope, or redirect_url
both of these values CAN have default registered values in IMS
Currently if we pass scope:null, or callbackUrl:null to this function, it will add &scope=null to the url which will fail.

done like dinner


:bug: avoid silent auth crashes

I have not tested that this works, I don't know of a good way to test this so if anyone has any good ideas I am all ears.

Best way to test is by using the bulld and use script

Best way to test is by using the bulld and use script

Sure, but this is related to the silent auth to get a new access token after the initial one expires

Did work to edit the localstorage to trigger the error?

Did work to edit the localstorage to trigger the error?

Unfortunately, no. I tried to remove only the access token, then the access toke and reference id, then all msal related key/value pairs, and finally the entire local storage. Nothing triggered the error :/
Also we copy the auth.html file over implicitly when running docker, it is located in the public folder which we copy over


feat(wasm): add transformer target API

#7513  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Nov 27, 10:38 PM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.


Ta salesforce screenshots

Domino REST API Documentation Update
Change description
Added screenshots for Salesforce
Due diligence

[ ] tested locally using bundle exec jekyll serve

Review/Merge

[x] Ready for review
[x] Ready for merge

Follow-up work
List any out-of-scope work that you identified

 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.Tanya Anurag seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Update JSLoader.cpp

Since react-native-cli is deprecated, the correct command should be npx react-native start

ping @grabbou @kelset


v4 frequency script

Here is the full frequency script. I've run it on the test dataset using the --use-test-dataset arg. The script currently puts out all of the annotations from the split VDSs and any annotation used in correcting for the high AB hets. I plan on removing these once this is ready and have a note before the final write on which fields I plan on removing for now. I also realized this does not account for the downsamplings within the ukb subset which Konrad had asked for so I will work on adding that but figured this is huge so should not hold up review with it. As I mentioned in one of our chats, I copied Tim's freq updates and then updated them here to account for the upstream downsampling annotation. Post v4, I will rewrite the gnomad_methods annotate_freq method. This depends on the code added in https://github.com/broadinstitute/gnomad_methods/pull/565  so will fail checks until that is in.

I'm realizing the non-ukb subset needs to have its own grpmax and age hists and this code doesnt currently account for that. Since we are already splitting by ukb, this should be easy enough to add in but I wont until we get through one round of review.

KC approved the structure and schema output via slack, will merge once we resolve the pylint check:https://github.com/broadinstitute/gnomad_qc/pull/416


Update sbt-assembly to 2.1.3

About this PR
📦 Updates com.eed3si9n:sbt-assembly from 1.2.0 to 2.1.3 ⚠
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.eed3si9n", artifactId = "sbt-assembly" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.eed3si9n", artifactId = "sbt-assembly" }
}]

labels: sbt-plugin-update, early-semver-major, semver-spec-major, commit-count:1

Will skip updates until this is resolved, since we need the mappings: https://github.com/sbt/sbt-assembly/issues/497


Update troubleshoot.md

Fix address when calling insecure gRPC service.

@JamesNK  let me know when I can S&M.

Go ahead


[otel-demo] Include namespace in NOTES.txt

For full copy & paste, the port-forwarding instructions need to  include the namespace.

@TylerHelmuth done.
I wonder if this step could be done in CI once a commit hits main

@dependabot rebase


Example codes Error

there's some error in Example -> Header -> HeaderView.
i don't analyze deeply, but i build example app and run, app runs well except headerview.
when i click header above menu, the view is show. after then, i touch any cells, the above photo is dismissed suddenly. just one time, others is fine.
i move back to first Examples tableview, and touch Header above menu, touch any cell. the issue that suddenly above photo is dismissed is still exsited,
please fix it for me! thanks.

please fix it for me!

This is just an example of what you can do with Parchment, and not part of the actual library. I will look into improving the examples, but you have to implement your own app yourself

实际上我认为属于库的一部分, 因为我运行了 Demo 在不同的设备上.
其中 Header abaove menu 在系统版本为 12.5.5 的 iPhone 6 上为预期显示正确,
然而在系统版本为 15.2 的 iPhone X 上, 显示的第一个 tableviewCell 被 menu 遮挡, headerView 没有显示出来, 滑动的时候才会正常.

所以我觉得是一个需要适配的地方


The Run All button tries to run all cells at the same time instead of sequentially

When I try to perform the process, it lunch all cells. It is possible to perform sequentially
Thanks

Thanks for this issue. Originally, I had considered the possibility of parallel execution a feature, but it now seems this is an unexpected UX for users coming from other notebook formats. Also see #30.


Github integration with repositories with a . in title does not work

If a github repo has a . in its name the Github integration will not work. Haven't looked into the platform.cli code but probably a simple parsing issue?
Error message receive is:
The option "repository" with value "roomify/roomify.us" is invalid.

Hi Ronald - this was fixed in v2.1.0: https://github.com/platformsh/platformsh-cli/commit/c1259bbd45caf2e9d921e950287b61eaa23f2ff3

Awesome - thanks!


Add support for Linux, macCatalyst, and visionOS

When we merge, I'll need to add the linux check and macCatalyst checks as required on all PRs.
We'll add visionOS checks to CI once Xcode 15.2 is generally available, but for now I've run tests locally on a beta install of Xcode 15.2.

Going to merge this through without waiting for approval since we're just adding explicit support for platforms we were already supporting.

As always, happy to address feedback post-merge 🙂


add option to stop passing paths to the linters

Description
We want to do a full TypeScript type check of the project before any .tsx? files is committed, typically we use tsc -p . --noEmit.
However if we integrate this command into lint-staged like this:
{
  "lint-staged": {
     "*.{ts,tsx}": "tsc -p . --noEmit"
  }
}

we got an error from tsc:
git commit
husky > npm run -s precommit (node v8.9.4)

 ❯ Running tasks for *.{ts,tsx}
   ✖ tsc -p . --noEmit
     → error TS5042: Option 'project' cannot be mixed with source files on a command line.
✖ tsc -p . --noEmit found some errors. Please fix them and try committing again.
error TS5042: Option 'project' cannot be mixed with source files on a command line.

husky > pre-commit hook failed (add --no-verify to bypass)

Environment

OS: macOS High Sierra
Node.js: v8.9.4
lint-staged: v6.0.0

lint-staged adds staged files as argument to your command, so there is a conflict of . and how lint-staged works. This is why you see this error. You should either do -p . and run it on precommit without lint-staged, or remove -p option.

Regarding the feature request. There is a duplicate issues already #138 so I'm closing this one.

For those that have arrived here in search of type-check TypeScript files on pre-commit hooks, see the gist below.
https://gist.github.com/dcurletti/89edd6a5b329fa01faf39148ffafa71a

We support function syntax for exactly this: https://github.com/okonet/lint-staged#example-run-tsc-on-changes-to-typescript-files-but-do-not-pass-any-filename-arguments

@okonet yes, but it seems to be impossible to do inside package.json,


⚠ Samsung has degraded performance

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

HTTP code: 200
Response time: 2594 ms

Resolved: Samsung performance has improved in 5304a98.