ENOENT while npm install

I ran into ENOENT while running npm install in the cloned project.
First time I ran npm install resulted in:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm ERR! Linux 3.13.0-98-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v6.8.0
npm ERR! npm  v3.10.8
npm ERR! path /var/node/myProject/node_modules/mocha/bin/mocha
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod

npm ERR! enoent ENOENT: no such file or directory, chmod '/var/node/myProject/node_modules/mocha/bin/mocha'
npm ERR! enoent ENOENT: no such file or directory, chmod '/var/node/myProject/node_modules/mocha/bin/mocha'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! Please include the following file with any support request:
npm ERR!     /var/node/myProject/npm-debug.log

Then, just out of curiosity because I couldn't find a solution, I kept running it.
Second time:
vagrant@vagrant-ubuntu-trusty-64:/var/node/myProject$ npm install

><EMAIL_ADDRESS>postinstall /var/node/myProject
> bower install --allow-root && bower prune --allow-root

bower angular#~1.5.0            cached https://github.com/angular/bower-angular.git#1.5.8
bower angular#~1.5.0          validate 1.5.8 against https://github.com/angular/bower-angular.git#~1.5.0
bower angular-animate#~1.5.0    cached https://github.com/angular/bower-angular-animate.git#1.5.8
bower angular-animate#~1.5.0  validate 1.5.8 against https://github.com/angular/bower-angular-animate.git#~1.5.0
bower angular-bootstrap#~1.2.1  cached https://github.com/angular-ui/bootstrap-bower.git#1.2.5
bower angular-bootstrap#~1.2.1         validate 1.2.5 against https://github.com/angular-ui/bootstrap-bower.git#~1.2.1
bower angular-mocks#~1.5.0               cached https://github.com/angular/bower-angular-mocks.git#1.5.8
bower angular-mocks#~1.5.0             validate 1.5.8 against https://github.com/angular/bower-angular-mocks.git#~1.5.0
bower angular-resource#~1.5.0            cached https://github.com/angular/bower-angular-resource.git#1.5.8
bower angular-resource#~1.5.0          validate 1.5.8 against https://github.com/angular/bower-angular-resource.git#~1.5.0
bower angular-ui-notification#~0.2.0     cached https://github.com/alexcrack/angular-ui-notification.git#0.2.0
bower angular-ui-notification#~0.2.0   validate 0.2.0 against https://github.com/alexcrack/angular-ui-notification.git#~0.2.0
bower angular-ui-router#~0.2.18          cached https://github.com/angular-ui/angular-ui-router-bower.git#0.2.18
bower angular-ui-router#~0.2.18        validate 0.2.18 against https://github.com/angular-ui/angular-ui-router-bower.git#~0.2.18
bower bootstrap#~3.3.6                   cached https://github.com/twbs/bootstrap.git#3.3.7
bower bootstrap#~3.3.6                 validate 3.3.7 against https://github.com/twbs/bootstrap.git#~3.3.6
bower ng-file-upload#^12.1.0             cached https://github.com/danialfarid/angular-file-upload-bower.git#12.2.12
bower ng-file-upload#^12.1.0           validate 12.2.12 against https://github.com/danialfarid/angular-file-upload-bower.git#^12.1.0
bower ng-img-crop#^0.3.2                 cached https://github.com/alexk111/ngImgCrop.git#0.3.2
bower ng-img-crop#^0.3.2               validate 0.3.2 against https://github.com/alexk111/ngImgCrop.git#^0.3.2
bower owasp-password-strength-test#~1.3.0           cached https://github.com/viaforensics/owasp-password-strength-test.git#1.3.0
bower owasp-password-strength-test#~1.3.0         validate 1.3.0 against https://github.com/viaforensics/owasp-password-strength-test.git#~1.3.0
bower angular-messages#~1.5.0                       cached https://github.com/angular/bower-angular-messages.git#1.5.8
bower angular-messages#~1.5.0                     validate 1.5.8 against https://github.com/angular/bower-angular-messages.git#~1.5.0
bower angular#>=1.4.0                               cached https://github.com/angular/bower-angular.git#1.5.8
bower angular#>=1.4.0                             validate 1.5.8 against https://github.com/angular/bower-angular.git#>=1.4.0
bower jquery#1.9.1 - 3                              cached https://github.com/jquery/jquery-dist.git#3.1.1
bower jquery#1.9.1 - 3                            validate 3.1.1 against https://github.com/jquery/jquery-dist.git#1.9.1 - 3
bower angular-bootstrap#~1.2.1                     install angular-bootstrap#1.2.5
bower angular-mocks#~1.5.0                         install angular-mocks#1.5.8
bower angular-ui-notification#~0.2.0               install angular-ui-notification#0.2.0
bower angular-resource#~1.5.0                      install angular-resource#1.5.8
bower angular-animate#~1.5.0                       install angular-animate#1.5.8
bower angular#>=1.4.0                              install angular#1.5.8
bower ng-img-crop#^0.3.2                           install ng-img-crop#0.3.2
bower ng-file-upload#^12.1.0                       install ng-file-upload#12.2.12
bower angular-ui-router#~0.2.18                    install angular-ui-router#0.2.18
bower bootstrap#~3.3.6                             install bootstrap#3.3.7
bower owasp-password-strength-test#~1.3.0          install owasp-password-strength-test#1.3.0
bower jquery#1.9.1 - 3                             install jquery#3.1.1
bower angular-messages#~1.5.0                      install angular-messages#1.5.8

angular-bootstrap#1.2.5 public/lib/angular-bootstrap
└── angular#1.5.8

angular-mocks#1.5.8 public/lib/angular-mocks
└── angular#1.5.8

angular-ui-notification#0.2.0 public/lib/angular-ui-notification

angular-resource#1.5.8 public/lib/angular-resource
└── angular#1.5.8

angular-animate#1.5.8 public/lib/angular-animate
└── angular#1.5.8

angular#1.5.8 public/lib/angular

ng-img-crop#0.3.2 public/lib/ng-img-crop

ng-file-upload#12.2.12 public/lib/ng-file-upload
└── angular#1.5.8

angular-ui-router#0.2.18 public/lib/angular-ui-router
└── angular#1.5.8

bootstrap#3.3.7 public/lib/bootstrap
└── jquery#3.1.1

owasp-password-strength-test#1.3.0 public/lib/owasp-password-strength-test

jquery#3.1.1 public/lib/jquery

angular-messages#1.5.8 public/lib/angular-messages
└── angular#1.5.8
<EMAIL_ADDRESS>/var/node/myProject
├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>  ├──<EMAIL_ADDRESS>  ├──<EMAIL_ADDRESS>  ├──<EMAIL_ADDRESS>  ├──<EMAIL_ADDRESS>  ├─┬<EMAIL_ADDRESS>  │ └──<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.

Third time:
vagrant@vagrant-ubuntu-trusty-64:/var/node/myProject$ npm install

><EMAIL_ADDRESS>postinstall /var/node/myProject
> bower install --allow-root && bower prune --allow-root

npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.

It seems correctly installed or am I mistaken? What is my problem here?
edit:
there is no Gruntfile, so running
$ grunt
obviously doesn't work.
So something is still missing I guess. Please advice.

I dont see any error on the 2nd and 3rd attempt, just WARNs. They should be ok. Have you tried installing on your home folder? Installing in the /var folder probably causing permissions issue.

I just did a fresh install using the master and got a clean install with no ERRs. are you still seeing issue, if so what is your node, npm and meanjs version? If not this issue can be closed.

Must have been a permission issue. Deploying and installing to the home folder works just fine. As this is a new project, I will simply adapt my environment to live in the home folder instead of my usual node folder. On the prod server it won't make a difference.
Thank you for the assistance and your time. Greatly appreciated!


Feature/automated soft credits  organizational gifts

Automated Soft Credits: Admin defined setting handling -- W-023032.
Critical Changes
Changes
Issues Closed
New Metadata

src/labels/CustomLabels.labels > stgHelpOrgOCRDefaultRole
src/objects/npe01__Contacts_And_Orgs_Settings__c.object > Default_Organizational_Contact_Role__c

Deleted Metadata

@joy-sfdo also gitHub is complaining there is a merge conflict in RD_Recurring_Donations_TEST.cls that needs to get resolved.

Hi @davidhabib, thanks for the code review. I'll review your comments and update the code accordingly.

I'm really looking forward to this!
Is there a place to look for the general spec of this feature as it's not linked to a prior github issue?

@riordan Nothing publicly available at this time. We'll be updating the pull request and related documentation as the feature nears release. Stay tuned. :-)

@joy-sfdo I just noticed that this pull request is trying to go into Master, rather than a parent branch that will hold all of the reviewed Automated Soft Credit work, so once all the pieces are in place and we are ready to publish to customers, we just merge the one reviewed branch.

@davidhabib -- That's interesting. I'll look into the branching.

@joy-sfdo Sorry if I hadn't been clear enough last week when I mentioned this.  We want to follow the same mechanism that rollups team is using.  Basically you would have branches like this:
/feature/AutomatedSoftCredits
/feature/AutomatedSoftCredits/workitem1
/feature/AutomatedSoftCredits/workitem2
/feature/AutomatedSoftCredits/workitem3
when any workitem is ready for a pull request, it is to /featureAutomatedSoftCredits, not Master.  this allows us to formally review and test it and merge it (in order to close the work item), without it going to customers.  The build system is automated to then push any change to /feature/AutomatedSoftCredits into the child branches (/workitem1, /workitem2, /workitem3) just like when a change to Master updates all our feature branches.
Once all the workitems are done, and we are ready to release to customers, all the code in /feature/AutomatedSoftCredits has already been reviewed, and we really just need to do some final testing before merging to master.
make sense?  I think Jason Lantz wrote up a doc on this, that you can probably find in quip.

@davidhabib -- That's the process that I used to set up the branches. As I mentioned, when we spoke I had created the branches in that fashion. I spoke to Chris Polcyn about the process of setting up Parent and Child branches and followed the steps the in Quip document (https://salesforce.quip.com/8F5aAdZBaK1r). I'll follow up on the branches.

@davidhabib -- Also, we can merge a branch into another branch as well.

@joy-sfdo looks like there is a compilation problem in the test orgs?  weird, since it deployed ok to my org.

@davidhabib -- Thanks for the update. I'll look into the compilation problems.


Port the tutor plugin from neovim

The github page for this plugin is at
https://github.com/fmoralesc/vim-tutor-mode
A slightly modified version of this is included in neovim. I have ported over
the plugin to Vim (with slight modifications).

So, at least part of this comes from the plugin from Felipe Morales?  Please ask him to put a license on his work.  Without a license we are not allowed to use it.  The Vim license would be best, like it applies to most of the runtime code.

Hi Bram,
On Tue, Jul 7, 2020 at 3:32 AM Bram Moolenaar<EMAIL_ADDRESS>wrote:

So, at least part of this comes from the plugin from Felipe Morales?
Please ask him to put a license on his work. Without a license we are not
allowed to use it. The Vim license would be best, like it applies to most
of the runtime code.

I reached out to Felipe Morales about the license. He has now added a
LICENSE file to the repository with reference to the Vim license.
https://github.com/fmoralesc/vim-tutor-mode/commit/e4e41af4bffadeae2549b4fa68e19b572313c286
Regards,
Yegappan

Yegappan wrote:

On Tue, Jul 7, 2020 at 3:32 AM Bram Moolenaar<EMAIL_ADDRESS>wrote:

So, at least part of this comes from the plugin from Felipe Morales?
Please ask him to put a license on his work. Without a license we are not
allowed to use it. The Vim license would be best, like it applies to most
of the runtime code.

I reached out to Felipe Morales about the license. He has now added a
LICENSE file to the repository with reference to the Vim license.
https://github.com/fmoralesc/vim-tutor-mode/commit/e4e41af4bffadeae2549b4fa68e19b572313c286

Great, that was quick.
Now we need to find out what in the current vimtutor is missing from
this plugin implementation.
--
Article in the first Free Software Magazine: "Bram Moolenaar studied
electrical engineering at the Technical University of Delft and
graduated in 1985 on a multi-processor Unix architecture."
Response by "dimator": Could the school not afford a proper
stage for the ceremony?
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

I finally found some time to look at this. I have my doubts if this is better than the existing vimtutor.  It looks nicer, but it also uses several mechanisms that take it away from "raw" Vim.  The tutor is especially made in a way that users can play around with the commands.  There should not be any surprises, such as hidden text (conceal mode is used) and signs popping up depending on what the text looks like.
Does someone have experience with giving this tutor to actual new Vim users?  A teacher perhaps.
Unless there is a clear advantage, I rather stick with the "old boring" tutor, since it has worked fine for a long time.

On Mon, Jul 4, 2022 at 7:46 AM Bram Moolenaar @.***>
wrote:

I finally found some time to look at this. I have my doubts if this is
better than the existing vimtutor. It looks nicer, but it also uses several
mechanisms that take it away from "raw" Vim. The tutor is especially made
in a way that users can play around with the commands. There should not be
any surprises, such as hidden text (conceal mode is used) and signs popping
up depending on what the text looks like.
Does someone have experience with giving this tutor to actual new Vim
users? A teacher perhaps.

Can anyone try the new tutor and give some feedback?
https://github.com/vim/vim/pull/6414
Thanks,
Yegappan

Unless there is a clear advantage, I rather stick with the "old boring"
tutor, since it has worked fine for a long time.

I've had a play with it. The makefile doesn't currently install the actual initial tutor (runtime/tutor/en/vim-01-beginner.tutor) so entering :Tutor in vim results in this error: "No tutorial with that name found". After moving the files to the expected location it runs well.
I do think that using this tutor is a much more pleasant experience than the standard vimtutor, and the signs changing from a red ✗ to a green ✓ when you've matched a line is nice feedback. However I also agree with Bram that the tutor should be simple, and there are some things that might be confusing due to use of conceal. For example, learning to use hjkl as the first first lesson and moving around a line becomes a bit confusing when you try to navigate over the links in "Lesson 0", as l appears to do nothing for a while (the cursor is moving over the concealed ](holy-grail    ) part of [like this](holy-grail    )).
There are also some bugs:

After completing section 3.1 (deleting and putting lines with dd and p) the signs no longer match up with the lines:

Actually after further testing I realise that this only happens if the 4th line is deleted. But after doing that and causing this issue:
In lesson 3.2 the X does not become a checkmark after correcting the line:

Note that this works correctly unless the section 3.1 error has been triggered.

I didn't test further. Overall it seems like a good idea to me but might need to be more robust?

I didn't test further. Overall it seems like a good idea to me but might need to be more robust?

Having said this, the original tutor is still there, so someone following a 10 year old recommendation to run "vimtutor" from the command line will still see the normal old tutor - which is good. Having this version as an optional plugin is a nice addition.

I don't like the new tutor (but it's only my opinion; I'm not a teacher).

The concealed text is indeed annoying and confusing.
With those check marks, it feels more like a test than a tutorial. The user tends to complete them rather than explore what they can do with the thing they just learned. When I read such tutorials (Vim's old one, an Emacs one, and a helix one) I tend to try operations that the text doesn't tell me to do and understand the result. The check marks discourage this.
Too many fancy stuff. The user will wonder how it's implemented since the tutorial itself is a text buffer in the editor. The plain text one will make the user focus on the basics it's teaching.
The first page doesn't teach how to move cursors. The new user won't be able to read further without other materials.
It uses existing config files, so that the behavior may be different than what the tutorial says. Those config files can be installed by a system admin on a shared machine, or by the user with OS package managers, or the OS tries to ship some "sane default" config, or the user followed a tutorial to install a customized suite but now they want to learn the basics.
There is no translation yet (but this could be improved later).

I include this as an optional plugin. Thanks all


No route matches [GET] "/blocks/edit_overview"

Hello!!
First Thanks u for your plugin...
Do you know how can I fix this problem?
Thank u!

Started GET "/blocks/edit_overview?project_id=ticketing" for <IP_ADDRESS> at 2016-08-19 16:58:04 +0200
ActionController::RoutingError (No route matches [GET] "/blocks/edit_overview"):
actionpack (3.2.19) lib/action_dispatch/middleware/debug_exceptions.rb:21:in call'   actionpack (3.2.19) lib/action_dispatch/middleware/show_exceptions.rb:56:incall'
railties (3.2.19) lib/rails/rack/logger.rb:32:in call_app'   railties (3.2.19) lib/rails/rack/logger.rb:16:inblock in call'
activesupport (3.2.19) lib/active_support/tagged_logging.rb:22:in tagged'   railties (3.2.19) lib/rails/rack/logger.rb:16:incall'
actionpack (3.2.19) lib/action_dispatch/middleware/request_id.rb:22:in call'   rack (1.4.7) lib/rack/methodoverride.rb:21:incall'
rack (1.4.7) lib/rack/runtime.rb:17:in call'   activesupport (3.2.19) lib/active_support/cache/strategy/local_cache.rb:72:incall'
rack (1.4.7) lib/rack/lock.rb:15:in call'   actionpack (3.2.19) lib/action_dispatch/middleware/static.rb:63:incall'
rack-cache (1.6.1) lib/rack/cache/context.rb:140:in forward'   rack-cache (1.6.1) lib/rack/cache/context.rb:249:infetch'
rack-cache (1.6.1) lib/rack/cache/context.rb:189:in lookup'   rack-cache (1.6.1) lib/rack/cache/context.rb:66:incall!'
rack-cache (1.6.1) lib/rack/cache/context.rb:51:in call'   railties (3.2.19) lib/rails/engine.rb:484:incall'
railties (3.2.19) lib/rails/application.rb:231:in call'   rack (1.4.7) lib/rack/content_length.rb:14:incall'
railties (3.2.19) lib/rails/rack/log_tailer.rb:17:in call'   rack (1.4.7) lib/rack/handler/webrick.rb:59:inservice'
/usr/lib/ruby/2.1.0/webrick/httpserver.rb:138:in service'   /usr/lib/ruby/2.1.0/webrick/httpserver.rb:94:inrun'
/usr/lib/ruby/2.1.0/webrick/server.rb:295:in `block in start_thread'

redmine_error-log.txt

Hi Daniel,
I’m not actively maintaining this plugin any more. It looks like the route
has been changed in a later version of Redmine so that /blocks/edit_overview is
no longer a valid route. If you want to submit a pull request for a fix I
am happy to merge it for you.
On 19 August 2016 at 16:14:29, Daniel Calle Rosa<EMAIL_ADDRESS>wrote:
Hello!!
First Thanks u for your plugin...
Do you know how can I fix this problem?
Thank u!
Started GET "/blocks/edit_overview?project_id=ticketing" for <IP_ADDRESS>
at 2016-08-19 16:58:04 +0200
ActionController::RoutingError (No route matches [GET]
"/blocks/edit_overview"):
actionpack (3.2.19)
lib/action_dispatch/middleware/debug_exceptions.rb:21:in call'
actionpack (3.2.19) lib/action_dispatch/middleware/show_exceptions.rb:56:in
call'
railties (3.2.19) lib/rails/rack/logger.rb:32:in call_app'
railties (3.2.19) lib/rails/rack/logger.rb:16:inblock in call'
activesupport (3.2.19) lib/active_support/tagged_logging.rb:22:in tagged'
railties (3.2.19) lib/rails/rack/logger.rb:16:incall'
actionpack (3.2.19) lib/action_dispatch/middleware/request_id.rb:22:in call'
rack (1.4.7) lib/rack/methodoverride.rb:21:incall'
rack (1.4.7) lib/rack/runtime.rb:17:in call'
activesupport (3.2.19)
lib/active_support/cache/strategy/local_cache.rb:72:incall'
rack (1.4.7) lib/rack/lock.rb:15:in call'
actionpack (3.2.19) lib/action_dispatch/middleware/static.rb:63:incall'
rack-cache (1.6.1) lib/rack/cache/context.rb:140:in forward'
rack-cache (1.6.1) lib/rack/cache/context.rb:249:infetch'
rack-cache (1.6.1) lib/rack/cache/context.rb:189:in lookup'
rack-cache (1.6.1) lib/rack/cache/context.rb:66:incall!'
rack-cache (1.6.1) lib/rack/cache/context.rb:51:in call'
railties (3.2.19) lib/rails/engine.rb:484:incall'
railties (3.2.19) lib/rails/application.rb:231:in call'
rack (1.4.7) lib/rack/content_length.rb:14:incall'
railties (3.2.19) lib/rails/rack/log_tailer.rb:17:in call'
rack (1.4.7) lib/rack/handler/webrick.rb:59:inservice'
/usr/lib/ruby/2.1.0/webrick/httpserver.rb:138:in service'
/usr/lib/ruby/2.1.0/webrick/httpserver.rb:94:inrun'
/usr/lib/ruby/2.1.0/webrick/server.rb:295:in `block in start_thread'
redmine_error-log.txt
https://github.com/tastapod/redmine_blocks_layout/files/427277/redmine_error-log.txt
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tastapod/redmine_blocks_layout/issues/19, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAAMbAUotG6fh47zZ9sCpTezzFhUT71Nks5qhchUgaJpZM4JoknM
.

Thanks for all.I will say to the new company redmine mantainer.


Unclear why exercise is locked

In this case it is not clear why an exercise is locked.

I checked the dependency json and there are a lot more deps not connected in the graph. Is there something that can be done about that?

That is a good point.
In that particular situation, do you know which of the dependencies is blocking the Maps concept?

That looks like an issue with the graph rendering rather than something specific to the go repo.
The maps concept has 5 prerequisites: https://github.com/exercism/go/blob/4ed2ad1680b80ea55d0cf13aaa4fb2f675d40932/config.json#L165-L169
Only the last one (functions) is being shown in the UI. It is missing all of the others like "conditionals-if" and "numbers". I think this issue belongs in a component where the UI rendering for the graph is written, but I do not know which component that is. Maybe we can start by moving it to exercism/exercism?

This is intentional to avoid too many lines in the concept tree, see https://exercism-team.slack.com/archives/GC3K95MRR/p1639488266184100?thread_ts=1639483090.183400&cid=GC3K95MRR on Slack.
In the hover box it should say what is needed to unlock.
I will close this issue.
In case someone has a big problem with the current state, feel free to open an issue in exercism/exercism.

@junedev: I kind of expected this to be intentional, to not overload the graph with too many lines. The problem is, that the hover box does not show any information on prerequisites either.

As a student who doesn't know where to look in the config files, I currently can't find a way to get to this information. If it should be in the hover box, can you point me to the file where it should be added?

@tehsphinx Can you clarify what you mean by "the hover box does not show any information on prerequisites". The hover box screenshot you posted says that you need to unlock "Conditionals Switch". Is that not correct?

Oh, right. Didn't see that as I was expecting like a list of items needed to unlock this. My bad 😁


Problems with executing the extension

Hello!
I am having problems with installing rust_hdl_vscode.
I cloned the repository, but I am facing errors when i execute the extension.
My first guess would be that i am missing some files, that are required for execution.
I know that the rust_hdl_vscode repository is mainly responsible for the VS Code extension and the actual language Server is on the rust_hdl repository.
I am also a little bit confused by the paths in the extension.ts file.
const languageServerDir = ctx.asAbsolutePath(         path.join('server', 'vhdl_ls')     );
languageServer = path.join(         'server',         'vhdl_ls',         languageServerVersion,         languageServerName,         'bin',         languageServerBinaryName + (isWindows ? '.exe' : '')     );
In the above code samples from the extension.ts file, the path includes a folder named 'server', but i can't find a folder with this name in the extension. Is this something that should be automatically created or rather be manually created?
I am very new to the topic and would be grateful, if someone could explain how to get the extension running and files i am missing etc.
I am interested in the project, but haven't found any proper documentation yet.
PS: my goal is to integrate the language server in an own small extension

The extension downloads the latest language server from github release artifacts. In that way the server is always up to date without having to republish the extension itself.

When i execute the extension, i get an error. "The preLaunchTask 'npm: webpack' terminated with exit code 1.".
By pressing "Debug anyway", i get the errors like below:
Activating extension 'hbohlin.vhdl-ls' failed: Cannot find module 'c:\Users\Jakob\Documents\GitHub\rust_hdl_vscode\dist\extension' Require stack: - c:\Users\Jakob\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\loader.js - c:\Users\Jakob\AppData\Local\Programs\Microsoft VS Code\resources\app\out\bootstrap-amd.js - c:\Users\Jakob\AppData\Local\Programs\Microsoft VS Code\resources\app\out\bootstrap-fork.js - .
So in my case, the extension doesn't work by default...

Furthermore, the terminal-output is:
Executing task: npm run webpack

<EMAIL_ADDRESS>webpack
webpack --mode development

C:\Users\Jakob\Documents\GitHub\rust_hdl_vscode\node_modules\loader-runner\lib\LoaderRunner.js:146
if(isError) throw e;
^
Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:71:19)
at Object.createHash (node:crypto:133:10)
at BulkUpdateDecorator.hashFactory (C:\Users\Jakob\Documents\GitHub\rust_hdl_vscode\node_modules\webpack\lib\util\createHash.js:145:18)
at BulkUpdateDecorator.update (C:\Users\Jakob\Documents\GitHub\rust_hdl_vscode\node_modules\webpack\lib\util\createHash.js:46:50)
at SourceMapSource.updateHash (C:\Users\Jakob\Documents\GitHub\rust_hdl_vscode\node_modules\webpack-sources\lib\SourceMapSource.js:233:8)
at NormalModule._initBuildHash (C:\Users\Jakob\Documents\GitHub\rust_hdl_vscode\node_modules\webpack\lib\NormalModule.js:870:17)
at handleParseResult (C:\Users\Jakob\Documents\GitHub\rust_hdl_vscode\node_modules\webpack\lib\NormalModule.js:936:10)
at C:\Users\Jakob\Documents\GitHub\rust_hdl_vscode\node_modules\webpack\lib\NormalModule.js:1028:4
at processResult (C:\Users\Jakob\Documents\GitHub\rust_hdl_vscode\node_modules\webpack\lib\NormalModule.js:745:11)
at C:\Users\Jakob\Documents\GitHub\rust_hdl_vscode\node_modules\webpack\lib\NormalModule.js:809:5 {
opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
library: 'digital envelope routines',
reason: 'unsupported',
code: 'ERR_OSSL_EVP_UNSUPPORTED'
}
Node.js v18.14.1

I would suspect the nodejs version. The CI pipeline uses version 16.

That solved the problem for me. Thank you very much! :)


Feature/add click custom

Codecov Report

Merging #43 into develop will decrease coverage by 2.50%.
The diff coverage is 84.56%.

@@             Coverage Diff             @@
##           develop      #43      +/-   ##
===========================================
- Coverage    96.13%   93.62%   -2.51%
===========================================
  Files           22       26       +4
  Lines         1139     1381     +242
  Branches       138      184      +46
===========================================
+ Hits          1095     1293     +198
- Misses          27       57      +30
- Partials        17       31      +14

Impacted Files
Coverage Δ

anymotion_cli/click_custom/didyoumean.py
75.00% <75.00%> (ø)

anymotion_cli/click_custom/repl.py
78.20% <78.20%> (ø)

anymotion_cli/click_custom/__init__.py
84.00% <84.00%> (ø)

anymotion_cli/click_custom/help_colors.py
100.00% <100.00%> (ø)

anymotion_cli/commands/analysis.py
92.64% <100.00%> (ø)

anymotion_cli/commands/analyze.py
94.23% <100.00%> (ø)

anymotion_cli/commands/compare.py
92.30% <100.00%> (ø)

anymotion_cli/commands/comparison.py
96.82% <100.00%> (ø)

anymotion_cli/commands/configure.py
95.83% <100.00%> (ø)

anymotion_cli/commands/download.py
91.66% <100.00%> (ø)

... and 14 more

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 06b6789...2b93524. Read the comment docs.


Argument error on file upload

I've this error when I try to save a version on S3
[error] Task #PID<0.639.0> started from #PID<0.633.0> terminating
** (ArgumentError) argument error
    (crypto) :crypto.hmac_nif(:sha256, ["AWS4", {:awscli, "default", 30}], "20161218")
    (crypto) crypto.erl:766: :crypto.hmac/6
    (ex_aws) lib/ex_aws/auth/signatures.ex:14: ExAws.Auth.Signatures.signing_key/3
    (ex_aws) lib/ex_aws/auth/signatures.ex:7: ExAws.Auth.Signatures.generate_signature_v4/4
    (ex_aws) lib/ex_aws/auth.ex:55: ExAws.Auth.auth_header/7
    (ex_aws) lib/ex_aws/auth.ex:18: ExAws.Auth.headers/6
    (ex_aws) lib/ex_aws/request.ex:27: ExAws.Request.request_and_retry/7
    (ex_aws) lib/ex_aws/operation/s3.ex:44: ExAws.Operation.ExAws.Operation.S3.perform/2
    (ex_aws) lib/ex_aws.ex:41: ExAws.request!/2
    (ex_aws) lib/ex_aws/s3/upload.ex:41: ExAws.S3.Upload.initialize!/2
    (ex_aws) lib/ex_aws/s3/upload.ex:83: ExAws.Operation.ExAws.S3.Upload.perform/2
    lib/arc/storage/s3.ex:53: Arc.Storage.S3.do_put/3
    (elixir) lib/task/supervised.ex:94: Task.Supervised.do_apply/2
    (elixir) lib/task/supervised.ex:45: Task.Supervised.reply/5
    (stdlib) proc_lib.erl:247: :proc_lib.init_p_do_apply/3
Function: #Function<0.60039956/0 in Arc.Actions.Store.async_put_version/3>
    Args: []

My config is the following:
config :arc,
  storage: Arc.Storage.S3,
  bucket: System.get_env("AWS_S3_BUCKET") ||"project-development"

config :ex_aws,
  access_key_id: [{:system, "AWS_ACCESS_KEY_ID"}, {:awscli, "default", 30}, :instance_role],
  secret_access_key: [{:system, "AWS_SECRET_ACCESS_KEY"}, {:awscli, "default", 30}, :instance_role]

there are no env variables set for aws, I've a profile (in the snippet I've set default but locally I've the profile name I want to use)

Did you add :configparser_ex as a dependency? It is not included by default.

Also, what version of ExAws are you on?

@benwilson512 nope, I haven't read about :configparser_ex anywhere, anyway 1.0.0-rc.4

Pretty sure that awscli is just on master at the moment, and not in rc.4 I will be doing a release today that will include it.

@benwilson512 awesome thank you


[Documentation] Add new Build Process Document

This adds a new build process document outlining all of the ways that we build Foundation and the details of each build variant. This also updates our main README to point to this document highlighting the getting started steps for building Foundation.

Thank you!


Fix Page#url_title: no file extension

Just noticed that removing the construct_path private method from the Page class resulted in the url_path_title being different from what gollum expects: it was expecting the title without the file extension. This PR removes the file extension from the url_path_title is a straightforward manner, without the need for something like construct_path.
Question: is the desired behavior for the title to include the directory path? That was the point of construct_path, but won't that result in super long titles? I can remember there being an issue about that, but can't figure out what we decided now.

is the desired behavior for the title to include the directory path?

It used to be, but for 5.x we landed on the name of the page for the title with a breadcrumb to show the full path (by default, unless overruled by h1-title or metadata title).

Ah right, thanks! This should be better then.


use same ngrok url every time

First of all, thanks for this -- it's working great on my Pi.  Second, is there a way to use a fixed ngrok url, rather than a new one being generated every time?

Nevermind, it seems you have to upgrade to a paid ngrok plan to use a custom subdomain.

We have a tool called bst proxy. It is free and doesn't change the url. Look [here].(https://bespoken.tools)


New package: Makie-tutorial v0.1.0

Registering package: Makie-tutorial
Repository: https://github.com/gazfaris/MakieTutorial
Created by: @gazfaris
Version: v0.1.0
Commit: 522dc81887358cf04b06c271a5035799f4567289
Reviewed by: @gazfaris
Reference: https://github.com/gazfaris/MakieTutorial/commit/522dc81887358cf04b06c271a5035799f4567289#commitcomment-63824009

It does not look like this should be a package

This seems like it probably should not be registered and can be installed from URL.


Explicitly list out the commands for busybox.

This allows building the debug container without running busybox, which
is needed to build from mac OS or Windows.
Closes #117

Thanks!


Add assessment fields to "new assessment" form

https://www.usaon.org/apps/benefit-tool/survey/new
This page should include:

[x] Title: Unique name of survey
[x] Description: Narrative description of the survey topic
[ ] Year: Allows for repeated analyses to show change over time. Year is sufficiently precise. We should also track timestamps (opened_date, last_modified, published_date), but a user-defined 'year' field would be useful. TODO: Is the "version" field OK?
[x] Type: Current state or Alternative (possible future) state (checkbox)

We called this field "hypothetical" (boolean)

Independent features
These tickets are not part of the acceptance criteria for this ticket:

[ ] Private: Can this survey be viewed by non-registered members? (Or should it be restricted to individuals?) #120
[ ] Tags: This is a user-defined field that admins can and will edit. It creates additional flexibility in the analyis, for example allowing for a regionally- or thematically-focused analysis.
[ ] Respondents: List of respondents with edit-access this is a functionality change, may need a separate ticket #66  #67 #70
[ ] Status: In-progress, Published, Closed, Archived #262

@hazelshapiro is the year field still needed in MVP? Or is that replaced with version? We've also moved several checkboxes to independent tickets. Can you ensure those tickets are correctly milestoned?

I don't see that there is a version field. Can you clarify? The tickets look correctly milestoned - thank you! But I don't think that the "tags" field is captured anywhere.

I don't see that there is a version field

I meant conceptually; I believe we'd talked about a "version" field as a more abstract alternative to a "year" field, and we could use the "title" field to communicate the distinction between versions of the same assessment. E.g., if you're looking at a versioned assessment it might display as: Assessment #1 (v3): River Watch 2026 (assuming v1 was 2024).

But I don't think that the "tags" field is captured anywhere

Created https://github.com/nsidc/usaon-benefit-tool/issues/271

Oh, and could you also comment on the "Type" field in the top-level post? I added a question there that should have been a comment, my bad 😓


Adding axel7083 to org.yaml

In kubeflow/manifests/pull/2409 @annajung asked me to add myself to allow me to be added to a OWNERS file.
She also offered to be a sponsor. I also guess that this extend to @kimwnasptd since he is the one who asked me to add myself in a OWNER file.

Some merged PRs I made

https://github.com/kubeflow/manifests/pull/2435
https://github.com/kubeflow/kubeflow/pull/7116
https://github.com/kubeflow/kubeflow/pull/7198
https://github.com/kubeflow/kubeflow/pull/7211
https://github.com/kubeflow/pipelines/pull/9594

Thanks for all your contributions!
+1

/lgtm
/approve
Thank you for your contributions! Welcome to the community! Note: This is not a OWNER file, but a list of Kubeflow community contributors.


10 replace xrd file reader

[x] Adding pynxtools as a submodule
[x] Get the entire plugin workflow working

[x]  Running

[x] Write a general parser for

[x] xrdml
[ ] xye
[ ] udf
[ ] raw

[x] General normalizer to fill NeXus template from file parsers (inside reader)
[x] Set a pipeline for getting NeXus template in plugin schema
[ ] Test Plugin in Nomad
[x] Add a normalize step in the plugin to fill up the NeXus section in Nomad.

@hampusnasstrom, once I am done with the ci in pynxtools and nomad then I would urge to test the plugin in nomad and give a feedback.
Other are, the different types of files:

At this time the reader is working only for a specific version of xrdml. The entire workflow should be accepted first. Then we have to sit together on how can we progress for other versions of the XRDml file. How many versions are available? Once we reach a satisfactory level for xrdml type file, we will proceed with other file types e.g. xye, udf, raw.

Hi @hampusnasstrom, once I am done with the ci in pynxtools and nomad then I would urge to test the plugin in nomad and give a feedback.
Other are, the different types of files:
1. At this point the reader is working only for a specific version of xrdml. The entire workflow should be accepted first. Then we have to sit together on how can we progress for other versions of the XRDml file. How many versions are available? Once we reach a satisfactory level for xrdml type file, we will proceed with other file types e.g. xye, udf, raw.

Sarthak and I are currently implementing .xrdml (without xrayutilities) and .rasx in a standalone reader for now. We will then have a look at other file types as we get requests from users.
I will later suggest some changes in your code after we have done some refactoring. We discussed in area A and think it best to extract the read and write into functions like Markus is suggesting here: https://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/blob/develop/docs/explanation/processing.md?ref_type=heads#strategies-for-re-usable-processing-code


Checksum does not appear to work

When running the following block:
seven_zip_archive "test" do
  path 'c:\\'
  checksum '<some checksum>'
  source '<local or http path>'
end

My expectation is that if checksum matches; that the zip file will NOT be extracted.  However, no matter what I put in for a checksum, the zip file is always extracted.
Any suggestions?

seven_zip resource is not idempotent by design.
Just use File.exist? to prevent run on each converge:
seven_zip_archive 'extract installer' do
  source url
  path Chef::Config['file_cache_path']
  overwrite true
  checksum node['example']['checksum']
  not_if { File.exist?(zip_path.to_s) }
  action :extract
end


Reverse String using Stack in C++

💥 Proposal
(A clear and concise description of what the proposal is.)
Have you read the Contributing Guidelines on Pull Requests?
YES

/assign


Improvements to this repo before SfN?

I'd like to add a link to this wiki on the SfN poster, and to point people here more generally that want to get started w/ the spec. What other information are we missing? Anything important? I have a few cycles of time to work on this in the next week or two, so wanna make sure it's being spent effectively!

Would it be useful to have a full iEEG template with all the sidecars with empty fields? I started this, but need to add the _channels.tsv, _electrodes.tsv and _electrods.json templates

I think a template would be great. In terms of having all the JSON files w/ empty fields, wasn't @chrisfilo working on a JSON schema along these lines? If there's a schema for BIDS, then that's also something we could use (or link to) here.

@chrisfilo thought that templates should be separate from json schema (schemas can be found in the validator: https://github.com/INCF/bids-validator/tree/master/validators/schemas)

Yeah that's a fair point. I was more thinking we could use the schema in order to generate a template. E.g., just write a script that parses the schema, strips the "description" fields etc, and puts it here. I'm just trying to minimize the number of pieces that move independently of one another.

I was creating two types of templates: 1) full templates with all optional fields, and 2) minimal templates, with only the required fields. For 2) I think we could potentially use schema files, but I did not see a json schema in the validator for fmap data, so I just started from scratch, see https://github.com/INCF/bids-starter-kit/pull/6

gotcha - makes sense then!


Do not parse horizontal lines

When I have the following markdown doc:
## Install

blah blah

---

blah blah

## Configure

blah blah

---

doctoc spits it like:
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
**Table of Contents**  *generated with [DocToc](https://github.com/thlorenz/doctoc)*

- [Install](#install)
- [](#)
- [Configure](#configure)
- [](#)

<!-- END doctoc generated TOC please keep comment here to allow auto update -->

## Install

blah blah

---

blah blah

## Configure

blah blah

---

It would be cool not to parse horizontal lines (---).

What version of doctoc are you using?

Interesting, 0.15. Upgraded to 1.0.0 and this is no longer an issue, thanks :)


Location Tool: Translate Tooltips

Bug
The shape creation tooltips are not translated, and I can't find where to translate them.
To Reproduce
Steps to reproduce the behavior:

Go to /location/new
Click on any shape tool
A tooltip with instruction appears, such as "Click first marker to finish," "Click to continue to draw," "Click to place first vertex," "Click to finish," "Click to place circle center," "Click to finish circle"

Expected behavior
Bug: These phrases are not localized, and I can't figure out where to localize them.
Solution: Please indicate where to translate these strings, and add a double-tilda to the strings.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

Win 10, FF 72

This is done.


fix: override http datasource logical IDs

Description of changes
This commit overrides the logical IDs of http datasources
created by the gql v2 transformer to prevent issues when
migrating from v1. It also renames the @http stack to be
consistent with v1.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #8714 (a161af4) into master (f798bbf) will decrease coverage by 0.00%.
The diff coverage is 25.00%.

@@            Coverage Diff             @@
##           master    #8714      +/-   ##
==========================================
- Coverage   56.92%   56.91%   -0.01%
==========================================
  Files         756      756
  Lines       42231    42233       +2
  Branches     8651     8651
==========================================
  Hits        24038    24038
- Misses      17372    17374       +2
  Partials      821      821

Impacted Files
Coverage Δ

...ify-graphql-transformer-core/src/transform-host.ts
24.79% <0.00%> (-0.42%)
:arrow_down:

...l-http-transformer/src/graphql-http-transformer.ts
98.34% <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 f798bbf...a161af4. Read the comment docs.


Add table azure_app_service_api_app

References
HIPAA requirement to check followings

Latest TLS version be used in API App
Remote debugging should be turned off for API Apps (in General Settings)

> select name,configuration -> 'properties' ->> 'remoteDebuggingEnabled' as remote_debugging_enabled from azure_app_service_web_app
+--------+--------------------------+
| name   | remote_debugging_enabled |
+--------+--------------------------+
| testqw | false                    |
+--------+--------------------------+

MinTLSVersion - MinTlsVersion: configures the minimum version of TLS required for SSL requests. Possible values include: 'OneFullStopZero', 'OneFullStopOne', 'OneFullStopTwo'
If the value is 1.2 then it is using latest.

> select name,configuration -> 'properties' ->> 'minTlsVersion' as min_tls_version from azure_app_service_web_app
+--------+-----------------+
| name   | min_tls_version |
+--------+-----------------+
| testqw | 1.2             |
+--------+-----------------+

This fundamentally addressed in the azure_app_service_web_app , which holds all type of apps (web & api). We may need to change the table to make it generic.


[WebToolsE2E][Aspire] Click Help on the Aspire Dashboard page, and the "Close" button prompt will automatically appear.

REGRESSION INFO: Worked in Aspire 8.2.1
INSTALL STEPS

Clean machine: Win11 x64 23h2 ENU
Install SDK 8.0.402
Install Aspire 9.0 RC1 [9.0.0-preview.4.24480.1]

REPRO STEPS

Open CMD, run following command to create an Aspire Starter App project

dotnet new aspire-starter -o AspireStarterApp
cd AspireStarterApp/AspireStarterApp.AppHost

Dotnet run the project in CMD, and open URL in the browser.
dotnet run

ACTUAL
Click Help, the prompt ‘Close’ will be automatically displayed.

Also reproduce the Add filter page in Structured and Traces

EXPECTED
When the mouse hovers over the close button, the prompt "Close" will appear.

This is a regression in fluentui-blazor, this appears in examples here
@v-reinawang could you file a ticket in microsoft/fluentui-blazor

I filed an issue in https://github.com/microsoft/fluentui-blazor

This issue has been fixed in latest Aspire 9.1.0-preview.1.24578.4.


only print test acc if loader available

Codecov Report

Merging #356 (84315f1) into master (0420c90) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #356      +/-   ##
==========================================
+ Coverage   95.33%   95.35%   +0.02%
==========================================
  Files         131      131
  Lines        4630     4631       +1
==========================================
+ Hits         4414     4416       +2
+ Misses        216      215       -1

Flag
Coverage Δ

unittests
95.35% <100.00%> (+0.02%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

domainlab/algos/observers/b_obvisitor.py
84.53% <100.00%> (+0.16%)
:arrow_up:

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Color: Info incorrect - update color values

Which page is this about?
Color: https://cfpb.github.io/design-system/foundation/color
Describe your issue

[x] The color values are outdated and need to be updated with the correct color values that Brenda put together in this doc:
CFPB Color Breakdown.txt
[x] When inputting the correct values, we need to make a note on the 10 values (i.e. Teal 10, Green 10, etc.) that a 10 value should only be used on the web and is too light for printing.
[ ] FYI as part of this, we'll need a dev's help to create new swatches to show in the tables for the new color values. (We've already created Mid Dark Green, Navy 50, Gold 70 and Purple 50 to show in the Data viz palettes.)
*Additional idea from George: We could consider renaming the mid dark and dark swatches to numerical values. So something like Navy 110 for Mid dark Navy and Navy 120 for Dark Navy. This would allow us to add even darker swatches in the future if needed. <--- I'm leaning toward leaving as is now and making change in future if/when we develop more swatches and have a need.

PR --> https://github.com/cfpb/design-system/pull/1049

Is this fixed now? If so, close it @anselmbradford @huetingj !


Avoid triggering auth in GCS backend tests

Q
A

🐛 Bug fix?
no

🚀 New feature?
no

⚠ Deprecations?
no

❌ BC Break
no

🔗 Related issues
#...

❓ Documentation
no

⚠ We should not do any operation in a New method. If the storage.NewClient is performing IO or network operations, it should be moved to the Read method.
We should not have to set GOOGLE_APPLICATION_CREDENTIALS in any test file because we are not supposed to reach GCP auth code in theses tests. That is a very hacky workaround, please open a tech debt issue or PR to handle this properly.


tdweb: missing support for reading file parts

From the tdweb source:
https://github.com/tdlib/td/blob/21dee3b1d923f3fdacc711b46ad102b1d0d1439b/example/web/tdweb/src/index.js#L25
However, the tdweb build used in telegram-react does have this functionality:
https://github.com/evgeny-nadymov/telegram-react/blob/35b69bc3d6fcd509f4ddd8e4287af483aed70fbb/public/tdweb.js#L4229-L4230
Any chance to add this to the build of tdweb too?

@Niek In fact, telegram-react uses pre-release version of tdweb with non-replaced readFilePart method and calls TDLib's readFilePart methods. TDLib in tdweb has no access to files after they are downloaded, because they are moved from memory to IndexedDB, so the method there doesn't work for fully downloaded files.

Support in tdweb for the non-zero offset and limit parameters in the method readFilePart was added in tdweb 1.4.1.

@levlam is this already in the tdweb build on https://www.npmjs.com/package/tdweb? Because that supposed to be 1.4.3 but the code still contains:
* 5. The method readFilePart supports only offset == count == 0.

This was removed in this tdlib commit a month ago: https://github.com/tdlib/td/commit/8ae3ac91a4b7c4a23746fd32c92e8c1baab23a06#diff-745180b5a943148d8e4f7d5f3fe7067c

@Niek It is in NPM since tdweb 1.4.1. In the mentioned commit only the documentation was updated.

Is there any sample on how to use readFilePart in tdweb? I tried calling the function in two ways:
readFilePart({path: update.file.local.path, offset: update.file.local.download_offset, size: update.file.local.downloaded_size}); always returns: "Error: File is not loaded at FileManager._callee8$".
readFilePart({file_id: update.file.id,                             offset: update.file.local.download_offset,                             count: update.file.local.downloaded_size}); (which is more in line with the docs) throws "count" and "filePart" errors.

@Niek Have you already downloaded the file using downloadFile? Could you show the whole file object?
count Number of bytes to read. An error will be returned if there are not enough bytes available in the file from the specified position.

@levlam No, the file is being downloaded and not completed yet. I assumed the readFilePart call would especially be useful for pushing chunks of partially-downloaded files (e.g. to enable streaming)?

@Niek Yes, it is. Could you show the file object, the readFilePart request and its response. All of them can be found in the tdweb info log.

Here's the update.file object:
{
    @type: "file",
    expected_size:<PHONE_NUMBER>,
    id: 7,
    local: {
        @type: "localFile",
        can_be_deleted: true,
        can_be_downloaded: true,
        download_offset: 0,
        downloaded_prefix_size: 1048576,
        downloaded_size: 1048576,
        is_downloading_active: true,
        is_downloading_completed: false,
        path: "/tdlib/inboundfs/temp/262"
    }
    remote: {
        @type: "remoteFile",
        id: "BQADAgADAwMAAuNfyUsOWwK4Mo67uhYE",
        is_uploading_active: false,
        is_uploading_completed: true,
        uploaded_size:<PHONE_NUMBER>
    }
    size:<PHONE_NUMBER>
}
```I'm not sure how to see the readFilePart request, I don't get a response either because it throws the error.

Yes, that's exactly what I'm doing now. It throws 2 errors in tdweb.js:2117:
{
    @extra: {
        query_id: 7
    },
    @type: "count",
    count: 1114112
}

and
{
    @extra: {
        query_id: 8
    },
    @type: "filePart",
    data: Blob {
        size: 1114112,
        type: ""
    },
    transaction_id: -2
}

It's from this code:
        (_console5 = console).error.apply(_console5, arguments);

Those errors are fine. It is just a debug with a wrong verbosity level.
Are you sure there is no answer to this query? It should be in the log shortly after the error. The log entry starts with "receive ".

You are right - it's working fine with the changed signature. I didn't look further because of the errors being dumped. Thanks for the help!


I was trying out the Customization sync, and say this phrase "Select all Shiny" what does this mean. What is the use case when the files are same. It hinders the way for "Apply all selected" as those also get applied which are all the same.
This gets weirder when it is done for all the plugins. Why select it when all are the same ??
Isn't this inefficient sync ??

Thank you for opening the issue!

"Select all Shiny"

This button allows us to choose all files which have the newest modified time in each group.
The use case is straightforward when we want to apply the newest changes to the current device.
Simply Newer things are chosen. And, why we do not filter Newer but the Same out is for the plug-in which cares about the modified time.
However, I am not sure about the behaviour which you pointed out --  everything the same is selected. It should not be selected.
Would you mind if I ask you to check the following things?

Are these things still selected If you tap Deselect all once and tap Select all shiny?
Are all of your things selected? Or, some specifics are always selected?
Would you mind sharing the report? (We can make it in the Hatch pane).

I came here looking for that explanation. This dialog might benefit from some QoL clean-up. "Shiny" seems like it maybe a technical jargon that many not know (I assume the shiny means "newer")?
Some possible UI alteration suggestions:

Button Filter (to hide/show) All w/ Time Difference
Button Filter (to hide/show) All w/ Content Difference
Add a tooltip or descriptive box to dialog that explains the different selector buttons (e.g. Select All Shiny), Maintenance Mode, and the other user-selecting options.

There's a "Hide Not-Applicable Items" checkbox, but that seems to be very selective, and only hides the elements that are both equal in timestamp and content (?), which is very little with so many plugins.


isOpen Method on TransactionalGraph

If a graph has been commited or rolled back there is no way to tell.
We have to keep our own state if we have committed the graph so we can deal with automatically rolling back in a finally block.

Such things are resolve in TinkerPop3:
http://www.tinkerpop.com/docs/3.0.0-SNAPSHOT/#transactions
http://www.tinkerpop.com/javadocs/3.0.0.M6/core/com/tinkerpop/gremlin/structure/Transaction.html#isOpen--
As we have frozen major development on the TinkerPop 2.x line of code, I don't imagine we will make such an interface change here at this point.  Thanks.


1.8 regression: dashboard has duplicate datasource

cc @carolynhu

Current status:

Mesh dashboard: datasource: default
Sevice and Workload dashboard: datasource: prometheus and default
Control plane dashboard: datasource: default

I'm going to remove the duplicated datasource, and use Prometheus as the source of truth


Precedence or context

Currently #\return and (return nil) both color return with the variable face. Fixing this with some source-aware context knowledge would be nice, as it fundamentally cannot be done with regular expressions alone.

True. And the same thing happens if you use any built-in function as a variable name.
For example in
(let ((list '(1 2 3))))

list will be rendered as a function instead of a trivial variable name.

Closing for archival


Test Api Token access in Verify Conditions step

Create package(s).

A. Pack with previous, latest, or minimum prerelease version; push it with --skip-duplicate.
B. Bundle a minver, deterministic-ated dummy package. Make one copy per Package ID. Push each dummy package with the real private keys. NuGet.org has a QA server that should work in lieu of --dry-run. Can we unlist specific package versions without unlisting the entire package?

Push package(s) to configured registries with private keys. If multiple package ID per registry, there may be as many as one private key per package ID for that registry. As noted, Nuget.org should be replaced with https://int.nugettest.org/ for the sake of token verification.

I started working on something similar when I realized it would be a great feature to have in this project! No more partial, failed releases because a package failed to push!

Hi there,
first of all, I understand the pain of having a release and failing the push, did encounter it myself last time my NuGET API key expired and I forgot to update the secret in a repo.
However I don't like the idea of pushing a package each time the verify step runs. Depending on the CI config it could run a lot of times, we don't even know if there is going to be a new release this time, because that is determined in a later step.
As for using the previous package this can be cumbersome, for once we don't necessarily have one, also it is not easy to determine what version it would have if we have one. Getting the last release is also done in a later step.
Unfortunately I don't really have a solution at this moment so other suggestions are welcome.

However I don't like the idea of pushing a package each time the verify step runs. Depending on the CI config it could run a lot of times, we don't even know if there is going to be a new release this time, because that is determined in a later step.

Performing token verification during prepare would solve part of the issue. Pushes would still need to run for each Token-Registry or PackageId-Token-Registry permutation. And that's assuming the packages are unsigned.
Performance hits could be mitigated by parallelizing via an array of calls to execAsync (where const execAsync = promisify(exec);) and Promise.all.
Bandwidth constraints and data limits aren't a concern. I learned how to to dotnet pack a 1.9 KiB dummy nupkg. It's just the minimum nupkg metadata files and a 0-byte Content file.

As for using the previous package, this can be cumbersome, for once we don't necessarily have one. Also, it is not easy to determine what version it would have if we have one. Getting the last release is also done in a later step.

Think of it as querying the latest version (incl. prereleases) of the package available from the registries. If there's no result with the exact PackageId, then the package has never been pushed to that registry.
Because GitHub and GitLab require tokens for queries of public endpoints and packages, they'll need to be dotnet nuget add sourceed with the token set as the password and username set to...anything. As an aside, it might be easier to tell users to set all NuGet sources before running semantic-release.
Finally, parse the output of dotnet package search $(PackageId) --format json --prerelease for results from each registry.
// dotnet package search HXE --format json --prerelease
{
  "version": 2,
  "problems": [],
  "searchResult": [
    {
      "sourceName": "Microsoft Visual Studio Offline Packages",
      "packages": []
    },
    {
      "sourceName": "gh-halospv3",
      "packages": [
        {
          "id": "HXE",
          "latestVersion": "2.1.3-ci.1",
          "totalDownloads": 0
        }
      ]
    },
    {
      "sourceName": "nuget.org",
      "packages": [
        {
          "id": "HXE",
          "latestVersion": "2.1.3-ci.1",
          "totalDownloads": 2715,
          "owners": "HaloSPV3"
        }
      ]
    }
  ]
}


Pass a list of architectures to support to Alizer

/kind feature
Parent user story: #6669
Which functionality do you think we should add?
As a user, I would like that Alizer returns a Devfile compatible with architectures I gave it.
Why is this needed?

Grooming (Jul 6, 2023)
@thepetk to create an issue in Alizer

@thepetk to create an issue in Alizer

Issue created here: https://github.com/devfile/api/issues/1181

Thanks @thepetk!

@rm3l this is still open in alizer side (to add support for the architectures). We are waiting the creation of more filters in devfile API


After run forge flatten command, then I run forge build, it shows: Multiple SPDX license identifiers found in source file.

Component
Forge
Have you ensured that all of these are up to date?

[ ] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (c5791f5 2022-11-11T00:05:26.949466Z)
What command(s) is the bug in?
forge flatten
Operating System
macOS (Apple Silicon)
Describe the bug
Firstly I run the forge flatten --output src/a.sol  src/Impl/b.sol  to flat my contract.
Then I run forge build.
It will give me an error:  ParserError: Multiple SPDX license identifiers found in source file. Use "AND" or "OR" to combine multiple licenses.

@KittyFu307 where are your license identifiers situated within the file? as far as i remember, we strip them only if they located on the very first line

@KittyFu307 where are your license identifiers situated within the file? as far as i remember, we strip them only if they located on the very first line

It's in the first line of my file

could you perhaps provide a repro for this?
all files, without all the contract code


decoder-quant.onnx , encoder-quant.onnx ,visual.onnx and textual.onnx

Thanks for the work, but could you describe in detail where to get the files decoder-quant.onnx, encoder-quant.onnx, visual.onnx and textual.onnx? As I understand it, they are very large, could you post them on Google Drive?

Thanks for the work, but could you describe in detail where to get the files decoder-quant.onnx, encoder-quant.onnx, visual.onnx and textual.onnx? As I understand it, they are very large, could you post them on Google Drive?

I have upload to release
https://github.com/AIDajiangtang/Segment-Anything-CSharp/releases/download/v1.0.1/ONNXModels.zip


sidebar's "My Stacks" section don't get updated on subscribing or unsubscribing the stacks

#168 Type of issue:

[x] Bug / Error
[ ] Idea / Feature
[x] Improvement detail

Short description on the issue
when the stack is subscribed or unsubscribed the details / contents of "My Stacks" section in sidebar don't get updated. it gets updated when the page is reloaded.

Yes, this issue is still there.


Improve the alignment of different buttons(list, calendar, starred,

search) along with full utilization of screen space.
Fixes #1265
Changes:

All the different buttons(list, view, calendar and search bar) are aligned in a single row and the full width of the screen is utilized for showing the date navbar and the buttons.
Change "Show Starred" to "Starred" and "Show All" to "All".
The buttons are responsive and behave nicely on different screen sizes.
Removes the redundant and extra classes written for the search and the filter bar.

Screenshots for the change:

Schedule Page

Rooms Page

Demo Link

Event Site  : http://princu7.github.io/eventSiteWebApp
Server : http://secure-meadow-20680.herokuapp.com

@mariobehling @aayusharora @geekyd Please Review. Thanks!!

Codecov Report

Merging #1275 into development will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           development    #1275   +/-   ##
============================================
  Coverage        65.46%   65.46%
============================================
  Files                9        9
  Lines             1523     1523
  Branches           225      225
============================================
  Hits               997      997
  Misses             526      526

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 cbf63be...8056d52. Read the comment docs.

Thanks, but please adhere to former design decisions. I see this happening many times recently, when there is a UI enhancement - at the same time border distances, spaces alignments or something small gets changed resulting in another PR, where it is fixed and then something else is changed. How can we improve the quality of our process?
If I ask, someone will say point a) is true, but point b) was changed elsewhere. It is not my fault. Someone else did it. If you work in an area, please ensure common design practices are followed, e.g. distance to borders, alignments, common heights and design of buttons etc. Please see the screenshot below. What do you find you can improve in this PR?

@Princu7 It would be great if you could start to see these things yourself. If I would open issues now, it would be too much micro-management. The time to open an issue is already much longer than to fix each small item. The main goal is: Can you please see these kind of things and follow common design practices, please?

@Princu7
The points by @mariobehling are very valid. Can we start with selenium testing asap?

@mariobehling @aayusharora I am sorry. There were a lot of small things to improve and I failed to see the border issue already existing in the app. I will try to be more careful from next time.
Here are the updated screenshots with comparison
Schedule page

Before

After

Tracks page

Before

After

@aayusharora I have removed the font-size property of the search bar to set the font to the default font used in the web app. We can start with testing soon. As soon as this issue is fixed, we can go ahead with it. Thanks!!

@Princu7 Please check the Dates for calendar view and list view it seems to have changed, please make its position same for both views.

@geekyd Thanks. I will fix it :)

@mariobehling @aayusharora Sorry. There were many small changes to be done on this issue and I failed to see the existing border problem in the app. I will try to be more careful from now. I have made some progress. I am attaching many screenshots below for easier reviewing process.

Deployment Link: https://princu7.github.io/eventSiteWebApp.
Please review. Thanks!!

@Princu7 Ok, Let's go with Flexbox, for now, I have seen you have used flex-wrap which is good, just need to check how it wraps in case the number of dates will increase to 6 or more than 6.
Can you please check and provide the result?

@aayusharora Thanks for pointing out the issue. In both the PR implementation and the existing implementation, on adding more date-filters, they overflow on the mobile and the whole site becomes scrollable. To avoid that, I added the overflow: auto property and now only the date filter component is scrollable. Here are some screenshots to demonstrate this:

PR Implementation

Existing Implementation(same)

After adding overflow: auto

Thank you @Princu7. Perfect.
But, the same case should be handled on Desktop too. In case we have more than 6 dates which ( if we accommodate in a single row in flexbox) would produce small text which would be difficult to read.
We can make a separate issue for that.
Thanks.

@mariobehling Approve and Merge, please
LGTM.

@Princu7 Great job! There is one thing that needs to be fixed please check the screenshot. for tablet view (1024x768). The size of the stared button is too large.

@geekyd Thanks!! I have updated the PR. It should be fine now.
![screenshot from 2017-05-13 23-23-17]
(https://cloud.githubusercontent.com/assets/8847265/26027860/3c328594-3833-11e7-83a8-b8d28dd493c6.png)

Ok, let's iterate from here.


Add htmlTemplate Option

This can specify the whole htmlTemplate to allow more possibilities.

Hi @globin,
Thanks for the pull request.  I'm not sure I fully understand what you're trying to do here.  Is it that you can now specify the entire template instead of just the module part?  Can you perhaps provide an example of when you'd want to do this and why?  (which could form the basis of a unit test)  Did you intend to break/remove the existing htmlModuleTemplate feature?
There are a few technical problems with this pull request. We need to make sure that the existing tests all pass, and I don't see a new test added for this new feature.  You can run grunt release to run all the tests.  We need at least one new test for functional changes like this, but perhaps more.  Secondly, the documentation that you've added (which is much appreciated) seems to have some cross-referencing issues.  Please review that once you've gotten the tests all working.
Thanks for the PR.

Hi,
I'm not sure what's going on there in that failing test..
The goal is to have the possibility to make templates look like this:
export = '<div>...</div>';


Monitoring View: Dark and light theme messed up

Describe the Bug with repro steps

Create a project in VS code.
Add a workflow to your local project
Open the workflow.json file in designer and author a new workflow
Add any triggers and actions of your own choice.
Press F5 to build and run your project

6.Open overview page. Right + Click on workflow.json file and "Overview".
7.Copy call back URL from the overview page
8.Send the http request POST via Postman and wait for the response
9.Refresh the overview page and your should see your local run
10.Open the monitoring view for your run from the overview page
6. Verify the run details and action inputs and output

Expected: Dark and light theme should not be messed up
Actual: Dark and light theme messed up
What type of Logic App Is this happening in?
Standard (VSCode)
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
No response
Screenshots or Videos

Browser
VS Code
Additional context
VSIX Verison : 4.57.3

This issue gets fixed with the following PR: https://github.com/Azure/LogicAppsUX/pull/5397
We are cherry-picking it for the release


basic InstructLab technical knowledge

Prompt: What is InstructLab?
Original response:
InstructLab is a research infrastructure project funded by the European Union's Horizon 2020 research and innovation program. ...
New response:
InstructLab is an open-source platform designed to facilitate the creation, training, and deployment of large language models. It provides tools, libraries, APIs, and a taxonomy repository, all of which are compatible with the OpenGen project. InstructLab aims to lower the barrier to entry for developers who wish to contribute to large language models while ensuring that their contributions align with the project's goals. It achieves this by providing a set of best practices, a code of conduct, and a contribution guide. InstructLab also includes a suite of tools for easily creating new taxonomy repositories, managing existing ones, and contributing new skills or knowledge to the open source community. Overall, InstructLab is a comprehensive platform that enables developers to quickly get started with large language models while ensuring that their contributions are aligned with the project's goals and best practices.
Explanation:
This response is improved by providing a clear definition of InstructLab, its purpose, and the resources it offers. It also mentions the benefits of using InstructLab for developers, making it easier for the user to understand the concept.
Laborsaving Device: This response is a labors
Prompt:
How users can use InstructLab?
Original response:
InstructLab is a powerful tool designed to facilitate the creation and management of machine learning models, especially for those without extensive programming skills. Here are some ways users can utilize InstructLab:

Model Training: InstructLab allows users to train machine learning models using a simple and intuitive user interface. Users can upload their datasets, select the desired model, and initiate the training process. InstructLab supports a variety of machine learning algorithms, including linear regression, decision trees, random forests, and neural networks.
...

New response:
Users can use InstructLab through the provided API, which allows them to easily engage with the model and test out new skills. The API is designed to be user-friendly, even for those without a deep understanding of large language models. Users can also contribute new skills and knowledge to InstructLab through the provided repository on GitHub, where they can submit pull requests with their additions. The InstructLab team will review and merge appropriate contributions, ensuring that the model is continually improved and enriched with new capabilities over time.
** Explanation:
This instruction is clear, concise, and provides a direct answer to the question. It also includes the necessary resources for the user to proceed, making it easier for the GPT model to generate an appropriate response.
Prompt:
How users can contribute to the taxonomy repository?
Original response:
Users can contribute to the taxonomy repository in several ways, depending on their role and expertise. Here are some ways users can participate:

Taxonomy Contributors: These are users who have been granted access to the taxonomy repository and can create, modify, and delete taxonomy terms. They can also suggest new terms, review existing terms, and ensure the taxonomy remains up-to-date and accurate.
...

New response:
Contributions to the taxonomy repository can be made through pull requests on GitHub. Before submitting a pull request, users are encouraged to review the contribution guide and the taxonomy repository's code of conduct. All contributions must adhere to the formatting and style guidelines outlined in the contributing guide. Additionally, all contributions should be accompanied by a signed Contributor License Agreement (CLA). The CLA is required to ensure that all contributors are aware of and agree to the terms and conditions outlined in the agreement. By signing the CLA, contributors agree to grant the project owners a perpetual, non-exclusive, worldwide, royalty-free, sublicensable license to distribute, modify, and create derivative works of their contributions. The CLA also serves to indemnify the project owners against any claims that may arise from the use of the contributor's contributions. Overall, the CLA process is designed to protect both contributors and project owners, while also ensuring that all contributions are made in good faith and with the best interests of the project in mind. By following the contribution guide, reviewing the code of conduct, adhering to the formatting and style guidelines, and signing the Contributor License Agreement, users can ensure that
Prompt:
What does InstructLab consist of?
Original response:
InstructLab is a collaborative, interdisciplinary research project that brings together experts from various fields to develop new materials and technologies for the solar energy industry. The project is part of the Instruct-ERC (European Research Council) initiative, which supports cutting-edge research in Europe. InstructLab focuses on the following key areas:
...
New response:
InstructLab consists of a taxonomy repository, a training dataset, a repository of open source LLMs, a repository of open source chatbots, a repository of open source tools, a repository of open source libraries, a repository of open source APIs, a repository of open source CLI tools, a repository of open source InstructLab-compatible models, a repository of open source InstructLab-compatible chatbots, a repository of open source InstructLab-compatible tools, a repository of open source InstructLab-compatible libraries, a repository of open source InstructLab-compatible APIs, a repository of open source InstructLab-compatible CLI tools, a repository of open source InstructLab-compatible InstructLab-compatible training data, a repository of open source InstructLab-compatible training tools, a repository of open source InstructLab-compatible training libraries, a repository of open source InstructLab-compatible training APIs, a repository of open source InstructLab-compatible training CLI tools, a repository of open source InstructLab-compatible InstructLab-compatible testing data, a repository of open source InstructLab-
Prompt:
What does taxonomy repository of InstructLab consist of?
Original response:
The taxonomy repository of InstructLab is a comprehensive, curated collection of taxonomies and ontologies related to various domains. It includes taxonomies and ontologies from the following sources:

InstructLab Taxonomy Repository (ITR): This is the primary source of taxonomies and ontologies, maintained and updated by the InstructLab team. It contains taxonomies and ontologies developed in-house, as well as those contributed by the InstructLab community.
...

New response:
Taxonomy repository of InstructLab consists of freeform text or questions and answers that can be used to train LLMs. It includes a YAML file for each entry, specifying the context, question, and answer. The repository is organized into directories based on the topic or domain, making it easy for users to contribute and maintain the training data for LLMs. Additionally, the taxonomy repository is designed to be compatible with the InstructLab platform, allowing users to easily integrate their contributions and test their skills on the trained LLMs. Overall, the taxonomy repository is a crucial part of the InstructLab project, providing the foundation for developing and improving open-source LLMs while ensuring that the training data is curated, organized, and easy to manage.
** Explanation:
This response is improved by providing a clear explanation of what the taxonomy repository consists of, including the YAML files, topics, and domains, as well as the compatibility with the InstructLab platform. It also highlights the importance of the taxonomy repository in the InstructLab project, making the response more informative and easier to understand for the user.
Contribution checklist

[x] The contribution was tested with ilab generate
[x] No errors or warnings were produced by ilab generate
[x] All commits are signed off (DCO)
[x] The qna.yaml file contains at least 5 seed_examples
[x] The qna.yaml file was linted and prettified (yaml-validator can do both)
[ ] An attribution.txt file in the same folder as the qna.yaml file
[x] Content does not include PII or otherwise sensitive or confidential information
[x] Content does not include anything documented in the project's Avoid these Topics guidelines

Can you fix the linting issue please?

@instructlab-bot precheck

@instructlab-bot generate

The SDG looks very good. Approve for next training run.

What are obstacles to be approved?

We are waiting for our end-to-end run to be completed. It will be picked up in the next one, and we'll see how it changes the model upstream.
Unfortunately I can't tell you when it will be, but it is marked as "triage-approved," so it will be picked up.

Hi! :wave:
With the new update and release of 0.18.0, our base knowledge submissions have drastically changed. This has given us an opportunity to significantly improve the accuracy of our fine-tuned models, which is a major win for our community!
But alas, that has caused some changes that this PR isn't able to continue forward. We greatly appreciate the work you've put into this, and wish we could accept it but the amount of work to get it to be version: 3 is unrealistic for us to ask.
If you do want to do this, please don't hesitate to take the qna.yaml update it, and build it out. Otherwise, we hope you come back to our community with a new submission and help build out our Open Source community-driven LLM.
If you have any questions directly, please don't hesitate to comment on the PR or email me at awesomeATinstructlab.ai (yes, really), and I'll do my best to answer your questions.


Upload of large file fails with 400 Bad Request

Hey,
thanks for the great api! Listing files, downloading files or uploading small files works fine but I'm facing issue with larger files.
200 MB works fine, but the upload with
410 MB fails with with error message 400 Bad Request
I don't think it's a timeout as the response is returned after only 18 seconds.
Am I missing something? Maybe a property in the header?
I am grateful for all answers. Thanks in advance.
Below you can find the full stacktrace:
2021-11-08 15:45:34 DEBUG PLGSharepointClientOnline:454 - Uploading file<PHONE_NUMBER>667my-test.zip to folder /sites/mysite/Shared Documents/test folder/
2021-11-08 15:45:34 DEBUG StreamRestTemplate:147 - HTTP POST https://myurl.com/sites/mysite/_api/web/GetFolderByServerRelativeUrl('/sites/mysite/Shared%20Documents/test%20folder/')/Files/add(url='1636386334667my-test.zip',overwrite=true)
2021-11-08 15:45:34 DEBUG StreamRestTemplate:147 - Accept=[text/plain, application/json, application/*+json, */*]
2021-11-08 15:45:34 DEBUG StreamRestTemplate:147 - Writing [file [/data/jenkins_dev/workspace/DBU_Test_Job/my-test.zip]] as "application/json;odata=verbose"
2021-11-08 15:45:52 DEBUG StreamRestTemplate:147 - Response 400 BAD_REQUEST
org.springframework.web.client.HttpClientErrorException$BadRequest: 400 Bad Request
	at org.springframework.web.client.HttpClientErrorException.create(HttpClientErrorException.java:79)
	at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:122)
	at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:102)
	at org.springframework.web.client.ResponseErrorHandler.handleError(ResponseErrorHandler.java:63)
	at org.springframework.web.client.RestTemplate.handleResponse(RestTemplate.java:778)
	at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:736)
	at org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:637)
	at com.panxoloto.sharepoint.rest.PLGSharepointClientOnline.uploadFile(PLGSharepointClientOnline.java:471)
	at sharepoint.api.SharepointAPI.uploadFile(SharepointAPI.java:66)
	at sharepoint.api.SharepointAPI.main(SharepointAPI.java:39)

I have to look for a way to implement chunked file upload, as there is a limit in the rest API that limits max file upload size in a unique request.

@d-blum  I've added a uploadBigFiles implementing a chunked file upload that may allow to upload files up to 2Gb to Sharepoint Online. Not yet implemented in the On Premises version.
Notice that the group id of the artifact has also changed as i am planning to generate releases to maven central repository and the change was needed as if not i had to buy a domain.
I tested it with a 200Mb file and the upload is working.
An example call to the method could be this
 int chunkSize = 2048;
JSONObject result = client.uploadBigFile("YourLibraryOrfFolderToUploadWithoutSitePreffix",
				(Resource) new FileSystemResource(new File("/PATHTOYOURFILE)), metadata, chunkSize);

THe dir (first param) dont include de sites/..., only the path to the list or folder from the site.
metadata works as it worked before, with a json object with metadata to set to the document.
chunkSize is an int with the size of each chunk uploaded to the server.
Let me know if you have any issue with the solution to be able to close this issue.
Thanks

@kikovalle Unfortunately the new method does not work for me. I'm getting 404 NOT_FOUND. Below is the code I'm using:
client.uploadBigFile(pathToParentfolder, resource, new JSONObject("{}"), 2048);
The log is as follows:
2021-12-09 09:09:14 DEBUG StreamRestTemplate:147 - HTTP POST https://my.domain/sites/My-Site/_api/web/GetFolderByServerRelativeUrl('/sites/My-Site/Shared Documents/share/sharepoint-api-java/tests/uploadTests/')/Files/add(url='this is a small file.txt',overwrite=true)
2021-12-09 09:09:14 DEBUG StreamRestTemplate:147 - Accept=[text/plain, application/json, application/+json, /]
2021-12-09 09:09:14 DEBUG StreamRestTemplate:147 - Writing [Byte array resource [resource loaded from byte array]] as "application/json;odata=verbose"
2021-12-09 09:09:14 DEBUG StreamRestTemplate:147 - Response 200 OK
2021-12-09 09:09:14 DEBUG StreamRestTemplate:147 - Reading to [java.lang.String] as "application/json;odata=verbose;charset=utf-8"
2021-12-09 09:09:14 DEBUG PLGSharepointClientOnline:418 - Empty file created for chunked file upload
2021-12-09 09:09:14 DEBUG StreamRestTemplate:147 - HTTP POST https://my.domain/sites/My-Site_api/web/getfilebyserverrelativeurl('/sites/My-Site/Shared Documents/share/sharepoint-api-java/tests/uploadTests/this is a small file.txt')/startupload(uploadId=guid'123a123c-cc3e-49eb-b56d-720291074444')
2021-12-09 09:09:14 DEBUG StreamRestTemplate:147 - Accept=[text/plain, application/json, application/+json, /]
2021-12-09 09:09:14 DEBUG StreamRestTemplate:147 - Writing [[B@df4b72] as "application/octet-stream"
2021-12-09 09:09:14 DEBUG StreamRestTemplate:147 - Response 404 NOT_FOUND
In your project I've discovered the ChunkFileUploader. With the ChunkFileUploader I'm not facing an error 404 NOT_FOUND and the upload works as expected. The code for this approach is:
client.createChunkFileUploader().uploadFile(pathToParentfolder, resource, 5 * 1024 * 1024)
As there is a workaround that works for me I'm good with closing the issue.

I have an idea about the cause of the error, let me upload and update as i also detected a bug in last release.

Bugfix released with 1.0.4 version. Please let me know if the 404 error is solved for you. Thank you

I'm still getting the same error with version 1.0.4

I've just released 1.0.5 version i hope will solve the issue. Let me know  if it is solved, as i see in the exception it was related to the folder name and not to the upload logic itself.

Unfortunately it still does not work in version 1.0.5

I'm having this problem with 1.0.8 version.
Uploading small files are fine, but uploading big file with uploadBigFile method returns 404 FILE NOT FOUND


Fix Typo in NavigationServer2D

Thanks, and congrats on your first merged PR!

Cherry-picked for 4.0.3.


Update to released tcgc

Use latest dev version from npm.
Add cadl-ranch to dev dependencies and added rush script to start and stop the test server.
Removed unnecessary global installs for CI.

Dependent on https://github.com/Azure/autorest.go/pull/1159


Startup-Error when using MacPort vim with VimBox

mac-pro:VimBox robby$ vim
UltiSnips requires py >= 2.7 or py3
Betätigen Sie die EINGABETASTE oder geben Sie einen Befehl ein
But python is installed.

But did you install write Python enabled in the Mac port Vim? The instructions mention which vim this works with.

Ok, the version MacPorts installed by default doesn't has Python included.

sudo port install vim +cscope +huge +lua +python35

did the trick

I haven't tried any Mac ports but if you end up discovering an install process there that works, we can add it to list of supported MacVim builds. Until then, no promises anything works.

The vim (CLI version) via MacPorts works now as described above.

When using the binary from MacVim add this line to .vimrc to get it all working when using MacPorts Python:
let $PYTHONHOME="/opt/local/Library/Frameworks/Python.framework/Versions/Current"

Is there a reason to use the macports python instead of the default one?

Well, if you use macports you can get their Python installed as a dependency of something. Since macports takes higher priority in the search path, you know use the macports Python.
Overall it would make sense to cross-check if a macports Python is present and maybe ask the user which one to use or reference the macports version.

Yeah, sounds like a reasonable idea. If you can come up with a little snippet that does that, I'd be glad to include it so everyone can benefit.

I'm far from being a bash expert, here is a snippet that returns the macports Python path of the current active used Phyton version:
#!/bin/bash a=$(which python)  a+="-config" echo $a if read -r line < $a &>/dev/null ; then   echo macports pyhton used   echo $line   ppath=${line%s/*}   ppath+="/Current"   echo $ppath else   echo no macports phyton used fi
I'm sure it's not bullet proof but since we only target OSX, it should work.


First pass at GH Action to build docker-compose app container

Same structure as https://github.com/flowforge/helm/pull/43 for the helm builds.
No need to build the node-red container as it is currently the same as the one built by the helm build

fixes #32


How to Install Open Devin Locally

Hi everyone @jeremi @neubig  @mroch @penberg  @ohhmm  @JensRoland
I am trying to install OpenDevin locally on my system. While I have found some instructions on how to do this, I am encountering difficulties and would appreciate a detailed, step-by-step guide to ensure I set it up correctly. My goal is to clone OpenDevin, modify its prompts, and integrate it into my development workflow without having to pull the entire package each time.
Describe the UX of the solution you'd like
I would like a clear, comprehensive guide that covers the following aspects:

Prerequisites and system requirements for running OpenDevin locally.
Step-by-step instructions for installing all necessary tools and dependencies (e.g., Docker, Node.js, npm, Rust, Conda, etc.).
Detailed commands for cloning the OpenDevin repository and setting up the development environment.
Instructions for modifying the cloned version of OpenDevin, including how to integrate custom prompts and other changes.
Guidance on running OpenDevin in a Docker container using the local clone instead of pulling from the GitHub Container Registry each time.

Do you have thoughts on the technical implementation?
Here are some initial thoughts on the technical implementation:

Docker Configuration: I need to configure Docker to use a locally cloned version of OpenDevin. This might involve modifying the Dockerfile or using volume mounts to point to the local codebase.
Environment Setup: Detailed commands and configuration settings for setting up the environment in WSL (Windows Subsystem for Linux) or a native Linux environment.
Dependency Management: Information on managing dependencies using Conda, npm, and other package managers.

Describe alternatives you've considered
I have considered the following alternatives:

Following the existing installation guides available online, but they are either incomplete or do not address the specific need to use a local clone.
Using a virtual machine to set up a completely isolated environment, but this approach seems overly complex and resource-intensive for my needs.
Attempting to modify the Docker commands to point to a local directory, but I am unsure of the correct configuration.

Additional context

System Details: I am using a Windows system with WSL2 enabled. Docker is installed and running correctly.
Development Tools: I have experience with using Git, Docker, and basic command-line operations, but I am not deeply familiar with modifying Dockerfiles or complex environment setups.
Goal: My ultimate goal is to be able to make custom modifications to OpenDevin and run it locally in a way that is efficient and repeatable.

Any assistance or detailed guidance on how to achieve this setup would be greatly appreciated. Thank you!

我一直在关注这个项目，因为技术原因，一直没有运行成功，我也希望项目主能出一些能让小白新手一步步能运行起来，谢谢！

Google translate to English for the above: "I have been paying attention to this project, but due to technical reasons, it has not been successfully run. I also hope that the project owner can come up with something that can help novices start running it step by step. Thank you!"

Tbh the original version (chinese post) reads more like machine translation XD

After this, you should be able to visit the opendevin website. You might encounter some docker issues, but you can follow the documentation to resolve them.

hmm... instead of 4, 5 and 6: why not just "make build" and "make run"?
Are there issues with that we need to look into or is it just faster? 🤔

@tobitege
It might be because of my personal habit. I contribute to both the frontend and backend of opendevin. So, I prefer to start the frontend and backend separately.

@SM-Kumail-Rizvi the official ways to setup OpenDevin are:

Docker command: https://github.com/OpenDevin/OpenDevin?tab=readme-ov-file#-getting-started
Development workflow: https://github.com/OpenDevin/OpenDevin/blob/main/Development.md

Does that answer your question?
If you require a very specific setup, you can join the slack group and ask there to see if any developers can help you. However, the official documentation should work for setting up OpenDevin locally.


Add dependencies for JAX examples

It seems that our internal JAX container has removed cuda-python, so recent CI tests have been failing. This PR makes the requirement.txt s "include what you use".
Pinging @ksivaman and @jeng1220.

We also need cuda-python to check for cuda version for the fp8_autocast so the dependency should be in setup.

Actually, the cuda-python dependency seems to be removed in #198. I think it would be a good idea to update that PR so that we IWYU in the requirements.txt s.


Async export support

When implementing sync component model functions as async exports in JS (functions returning a promise), we should integrate with the event loop by:

Detecting if a promise is returned in the bindgen, and treating this as a special case which awaits the promise to get the result
In this same code, to have a function in the JS bindgen that performs increase_event_loop_interest() before awaiting the promise and decrease_event_loop_interest() on the promise then and catch handlers.
Creating a JS function in ComponentizeJS available to the bindgen which reflects these functions to StarlingMonkey's implementation of them
Calling run_event_loop in the main export function wrapper if there is event loop interest to resolve the return value

This is just a rough outline off the top of my head but hopefully it helps.

I do not understand the internals of the event loop yet. I just wanted to note that this seems like a regression in #111.
The behavior on the latest release seems to be the expected behavior where the guest seems to run until all the async tasks complete.

I think it's actually a bug that it was working before actually as the event loop architecture in StarlingMonkey has since changed. The technical counter-argument is that draining the event loop entirely risks allowing setInterval(() => {}) to saturate the compute. Exact event loop discussion is still active in https://github.com/bytecodealliance/StarlingMonkey/pull/56.

We (https://github.com/golemcloud/) are quite excited about this and the fetch support, so as an experiment with this idea we merged the current pending related PRs into forks (both on StarlingMonkey and ComponentizeJs), and then moved around a bit the interest markers and exposed "runEventLoop". This way after making a fetch request we can call explicitly the event loop, and by the time it returns, the fetch and related promises are nicely resolved and do work, which is quite promising, and would be something that we would be happy to live with until this topic evolves more.
On the other hand, repeated (10-100) calls to fetch in the same exported call and / or specific payload sizes (depending on the specific code) can trigger errors in the post_call phase, specifically in cabi_free. With node it results in "RuntimeError: memory access out of bounds" and similar errors are happening with wasmtime.
I do see that there is also a probably related issue on how the current "gc" is implemented (https://github.com/bytecodealliance/ComponentizeJS/issues/1), and probably this is a bit more complicated topic then i think, but wanted to ask if you might be able to provide any pointers on how one should continue debugging such errors or whether this is something that expected for now or if not, then it could be also added as a test case to the fetch ones.

This is now supported in https://github.com/bytecodealliance/ComponentizeJS/pull/131.


Add topologySpreadConstraints

@mumoshu done

@mumoshu I fixed build issue

@foxdalas apologies for the delay, change looks OK, could you resolve the conflicts 🙏


Add support for Guzzle client version 7.x.

The Guzzle API for versions 6.x and 7.x are very similar, so much so that in the case of this library the only requirement should be simply to add support for it.

I would love to see this merged. Can we merge this, please?

Need this for Laravel 8

Laravel 8 will also work with Guzzle 6 it just recommends to update it to 7, but it's not technically needed (https://github.com/laravel/laravel/pull/5381#issuecomment-689101352) but it would be nice to allow 7.x regardless 👍

Can we merge this please @gianarb @thecodeassassin ?

Merged and released version 1.15.1