[BUG]: Commmunication with the Streamdeck hardware not working after suspend & resume

In raising this issue I confirm that

[X] I have fully completed the issue template
[X] I have searched open and closed issues for duplicates
[X] I have read the Contribution Guidelines
[X] I have read the Code of Conduct
[X] I have read the Documentation

Describe the bug
After resuming from suspend, the display of my Streamdeck device turns on and stays on (even though I have set it to turn off after 10 seconds with the "auto dim after" setting), but pressing the buttons on my Streamdeck doesn't do anything. The interface of the streamdeck-linux-gui seems to respond, but communication with the Streamdeck hardware doesn't seem to work. I have to kill the program using the killall command to get everything working again. However, if I resume very quickly after suspend, I don't seem to have the problem. I don't think this problem was there initially; it appeared after some update a little while ago. I upgraded to Xubuntu 24.04 recently, but I don't remember if the problem started immediately after the upgrading to 24.04 or only a little bit later.
Steps to reproduce the behavior

Suspend the machine
Wait for more than just few minutes
Resume
Streamdeck-linux-gui is not able to communicate with the hardware anymore

Expected behavior
I would expect the program to be able to communicate with the Streamdeck hardware even after suspend & resume, without requiring killing of the software & restarting it.
Screenshots
Going through logs I noticed the following error messages. However, I am not sure if they are related to this problem:
StreamDeck.Transport.Transport.TransportError: No HID device.
raise TransportError("No HID device.")
File "/home/username/.local/pipx/venvs/streamdeck-linux-gui/lib/python3.12/site-packages/StreamDeck/Transport/LibUSBHIDAPI.py", line 254, in send_feature_report
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
return self.hidapi.send_feature_report(self.device_handle, payload)
File "/home/username/.local/pipx/venvs/streamdeck-linux-gui/lib/python3.12/site-packages/StreamDeck/Transport/LibUSBHIDAPI.py", line 399, in write_feature
self.device.write_feature(payload)
File "/home/username/.local/pipx/venvs/streamdeck-linux-gui/lib/python3.12/site-packages/StreamDeck/Devices/StreamDeckXL.py", line 106, in set_brightness
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
lambda brightness: self.decks_by_serial[serial_number].set_brightness(brightness),
File "/home/username/.local/pipx/venvs/streamdeck-linux-gui/lib/python3.12/site-packages/streamdeck_ui/api.py", line 209, in
self.brightness_callback(self.dimmed_brightness())
File "/home/username/.local/pipx/venvs/streamdeck-linux-gui/lib/python3.12/site-packages/streamdeck_ui/dimmer.py", line 92, in dim
self.function(*self.args, **self.kwargs)
File "/usr/lib/python3.12/threading.py", line 1431, in run
self.run()
File "/usr/lib/python3.12/threading.py", line 1073, in _bootstrap_inner
Traceback (most recent call last):
Exception in thread Thread-11:
System Information
*Xubuntu 24.04
*Xfce4
*Python	3.12.3
Stream Deck Version
Stream Deck XL

https://github.com/streamdeck-linux-gui/streamdeck-linux-gui/discussions/203


problem to connect in s3

hi, i have a problem to connect in s3:

Are you running inside a docker? If you use a stripped-down base image you may have to install ca-certificates.


Keep alive duration default and configurability

The default keep alive duration is 5 minutes and might too much in the context of an Android application.
I think we should:

make this configurable,
set it to a better default when running on Android.

The connection pool’s keepAliveDuration is configurable. No further action to take on this.


can't run on normal mode

it got crash (so far, i don't have any experience with electron, but it's seems to be electron is the problem here) as i tried to run mysam on server mode, it runs, but only showing the loading screen.
$ sudo mysam
bellow are the error logs:
sudo mysam
Error: Command failed: /bin/sh -c npm ls --depth 0 --parseable -g
npm ERR! max depth reached<EMAIL_ADDRESS>required by undefined@undefined
npm ERR! max depth reached<EMAIL_ADDRESS>required by undefined@undefined
npm ERR! max depth reached<EMAIL_ADDRESS>required by undefined@undefined
npm ERR! max depth reached<EMAIL_ADDRESS>required by undefined@undefined
npm ERR! max depth reached<EMAIL_ADDRESS>required by undefined@undefined
npm ERR! max depth reached<EMAIL_ADDRESS>required by undefined@undefined
npm ERR! max depth reached<EMAIL_ADDRESS>required by undefined@undefined
npm ERR! not ok code 0

    at ChildProcess.exithandler (child_process.js:215:12)
    at emitTwo (events.js:87:13)
    at ChildProcess.emit (events.js:172:7)
    at maybeClose (internal/child_process.js:817:16)
    at Socket.<anonymous> (internal/child_process.js:319:11)
    at emitOne (events.js:77:13)
    at Socket.emit (events.js:169:7)
    at Pipe._onclose (net.js:469:12)
Failed to get crash dump id.
Report Id:

That does look like Electron. I don't think you have to run with sudo but that probably doesn't make a difference in this case. I assume this is on Linux?

yes, i run it on Linux Mint,
Uncaught Exception:
Error: EACCES: permission denied, open '/usr/local/lib/node_modules/mysam/db-data/configuration'
    at Error (native)

when it runs without sudo.

This may be related to https://github.com/atom/atom/issues/4892 and I was able to reproduce the segfault in Ubuntu as well. I just released a new MySam version (0.1.4) with a newer version of Electron which fixed the issue for me. Please try installing that version and let me know if it works.

Closing since I could reproduce the issue and the fix. Please reopen if the problem still persists for you.

OK :+1:


Issue/5993 autocomplete null bug

Description
Previously opening the interfaces would crash the app as Autocomplete didn't handle null values
closes #5993
https://github.com/user-attachments/assets/571530ee-1ed5-4eb0-9bce-ccb433fdeaed
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[ x Code is clear and sufficiently documented
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Processing this pull request

Processing this pull request

Merged into branches master in f2845fafcb5a7bdc4dd32d434912879444ec3392

Not closing this pull request due to previously commented issues for some of the destination branches. Please open a separate pull request for those branches by cherry-picking the relevant commit. You can safely close this pull request and delete the source branch.

This branch was not deleted as it seems to still be in use.


Session persistence and restore

Background
A Session encapsulates the environment in which the Operation is executed, which contains a set of Operations, as well as the Graphs and Application, Context resources behind the Operations, which are loaded into memory.
Students who choose the task need to find a way to serialize the Operation and resources held by the session into persistent storage (such as disk/OSS), and provide a method for rebuilding Session with these resources from the serialized file.
Task Outcomes
Design solutions that can persist in-session resources and rebuild them from artifacts.
Develop corresponding methods for the design scheme, and contribute to the community.
Skills Requirement
Have some understanding of Kubernetes
Knowledge of languages such as Python, C++, etc.
Understand and be familiar with the use of GitHub, etc.
Difficulty
Basic
Mentor
@siyuan0322<EMAIL_ADDRESS>

I'm interested in further work. And other science problems about graphscope.

The design of this feature could be followed by PR #1986.
What I think is a function in python/graphscope/client/session.py called save_to(). As the requirement said it should only have the parameter path.  So I will fix it. And thanks for the advice by @siyuan0322.


change url via onSelect

This is a usage question, not a bug report.
I want the browser to open a certain url (in the current window) when the user selects an item of the autocomplete.
My code looks like this:
...
onSelect={(value, item) => {
const url = "/customer/" + item.id;
window.location = url;}
}
...
When an item is selected, nothing happens (the browser does not open the url). The weird thing is: When i place an alert("Hi") before the window.location assignment, it works (the browser does indeed open the url).
Any ideas what I am doing wrong? Thanks!

Can't reproduce your issue everything works as expected, could you please create online fiddle with this issue?

Thanks ,I finally found the error on my side. The react component was contained also in a form. So hitting enter triggered a form submit in addition to triggering the onSelect callback. Removing the form fixed it.


CP-SAT solver produces different results for the same model on different machines

What version of OR-Tools and what language are you using?
Version: 9.6.2534
Language: Python
Which solver are you using (e.g. CP-SAT, Routing Solver, GLOP, BOP, Gurobi)
CP-SAT
What operating system (Linux, Windows, ...) and version?
ubuntu:latest, Windows 10
What did you do?
I wrote a test function which solves a (simple) model with a fixed input and checks whether the result is as expected.
What did you expect to see
The test should pass in both environments with the same solution. There are 4 boolean variables which should have a value of 1 for the expected optimal solution.
What did you see instead?
The test always passes on my local windows machine (all 4 boolean values are equal to 1) and fails always on the Linux machine (3 of 4 boolean values are equal to 1).
If I check the attached logs I find that the initial model fingerprints are different. Also there are slightly differences in presolving phase:

line 61: [Probing]  - new integer holes: 25 (vs 26)
line 111:  - rule 'linear: simplified rhs' was applied 72 times.

linux_log.txt
windows_log.txt

Known result. Floating points are different across platforms.

If the fingerprints are different, then the models are different. Please create the same models.

Hi @lperron,
thx for your answer. From what I know, both models should be identical since they have been created using the same code & inputs. Could there be an other influencing factor leading to a different model?

Code is not always deterministic.
Hash tables are memory address dependent, and can differ across platforms,
sorting can differ...
If the fingerprints are different, the models are different.
Laurent Perron | Operations Research | @.*** | (33) 1 42 68 53
00
Le ven. 14 avr. 2023 à 12:54, PME93 @.***> a écrit :

Hi @lperron https://github.com/lperron,
thx for your answer. From what I know, both models should be identical
since they have been created using the same code & inputs. Could there be
an other influencing factor leading to a different model?
—
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/3748#issuecomment-1508325374,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUPL3JOQY2KAALO3PCLJGDXBEUHJANCNFSM6AAAAAAW6FYMFA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Latest NPM publish does not include render-voyager-page.js fix from #357

Hi,
I stumbled across Voyager for the first time today - great work!
Setting up the express middleware as per the readme leaves a dead "Loading" page in the browser. I can see this issue has already been fixed in #357 but the version hosted on NPM does not include this fix. I've patched my local version manually so I am able to use the software in the meantime.
I'm raising this issue primarily to draw attention as it affects all of the middleware offered - I think that's a big deal and would be considering a patch release as soon as practical.
Thanks again,
Matt

I have the same issue with version 2 and it is stuck in the "Loading" mode and the middleware version in Express.js is not working anymore so I have to downgrade to 1.3.0 for now. This is my code:
app.use(
  "/voyager",
  voyagerMiddleware({
    endpointUrl: env.endpoint
  }),
);

I have the same issue with version 2 and it is stuck in the "Loading" mode and the middleware version in Express.js is not working anymore so I have to downgrade to 1.3.0 for now. This is my code:

app.use(

  "/voyager",

  voyagerMiddleware({

    endpointUrl: env.endpoint

  }),

);

It's relatively easy to fix locally if you follow the issue I linked... you can just replace a single file in your node_modules.

I have the same issue with version 2 and it is stuck in the "Loading" mode and the middleware version in Express.js is not working anymore so I have to downgrade to 1.3.0 for now. This is my code:

app.use(

  "/voyager",

  voyagerMiddleware({

    endpointUrl: env.endpoint

  }),

);

It's relatively easy to fix locally if you follow the issue I linked... you can just replace a single file in your node_modules.

Thanks but I'm using voyagerMiddleware in my express app and deploying it to the server, so I'm not using it for the local development.

Thanks but I'm using voyagerMiddleware in my express app and deploying it to the server, so I'm not using it for the local development.

So am I, you can still fix as above.

Thanks but I'm using voyagerMiddleware in my express app and deploying it to the server, so I'm not using it for the local development.

So am I, you can still fix as above.

Can you share more details on how did you patch it?

Copy the file from the issue I linked in my first post into the node_modules/graphql-voyager folder in the correct location.
It's not a permanent solution because if you install somewhere else you need to update the file again... however for my purposes it was suitable.

Any chance this fix will get pushed sometime soon?


Make spl-token package compatible with Create React App and Webpack 5

New constraints on how modules must be imported and laid out in a distribution in CRA/Webpack 5 make it impossible to import the @solana/spl-token module.
In this PR, we update the build config to:

build .mjs files into the dist bundle
import indexes explicitly, since ESModules no longer support the implicit import './foo' syntax.

Note: This depends on https://github.com/solana-labs/buffer-layout-utils/pull/3 being released

I'll properly review this soon but

ESModules no longer support the implicit import './foo' syntax.

ಠ_ಠ
wtfff

For example, if we do an import './directory' from, say, a directory that has an index.js, ES modules do not look for an index.js file in the specified folder, as was the case in CommonJS. Instead, it throws an error.

https://blog.logrocket.com/es-modules-in-node-today/

Looks great. Thanks! I'll publish a new alpha version once I merge #2687


--show-statistics shows the errors in flake8 but not in ruff

@spaceone
With the repo: https://github.com/pyscript/pyscript
➜  pyscript git:(ruff) git mv setup.cfg setup.cfg.disabled  # Disables the flake8 config
➜  pyscript git:(ruff) flake8 . --max-line-length=100 --statistics
./examples/micrograd_ai.py:18:5: F821 undefined name 'pyscript'
    pyscript.write("micrograd-run-all-fig2-div", result)
    ^
./examples/micrograd_ai.py:24:5: F821 undefined name 'pyscript'
    pyscript.write("micrograd-run-all-print-div", "".join(print_statements))
    ^
./examples/micrograd_ai.py:80:5: F821 undefined name 'pyscript'
    pyscript.write("micrograd-run-all-fig1-div", plt)
    ^
./examples/todo.py:8:17: F821 undefined name 'Element'
task_template = Element("task-template").select(".task", from_content=True)
                ^
./examples/todo.py:9:13: F821 undefined name 'Element'
task_list = Element("list-tasks-container")
            ^
./examples/todo.py:10:20: F821 undefined name 'Element'
new_task_content = Element("new-task-content")
                   ^
./pyscriptjs/tests/integration/support.py:222:9: E731 do not assign a lambda expression, use a def
        pred = lambda msg: msg.text == text
        ^
1     E731 do not assign a lambda expression, use a def
6     F821 undefined name 'pyscript'
7

➜  pyscript git:(ruff) ✗ ruff check . --line-length=100 --statistics
1	E731	[*] Do not assign a `lambda` expression, use a `def`
6	F821	[ ] Undefined name `pyscript`

Flake8 shows both the errors and the summary
Ruff only shows the summary

Ah yeah, this was an intentional deviation. I thought it seemed not-so-useful to include the violations, since I see --statistics as a one- or few-time command rather than something that's included consistently. Are you using --statistics as a consistent flag on invocations?

Are you using --statistics as a consistent flag on invocations?

I was but I can live with this change.  Closing.


Support only publishing files added to git

This issue was originally filed by @Pajn

When running pub publish it wants to publish all files inside the project, it would be great with a flag to only publish files that are added to the git repository.
This is to avoid publishing build files, work-in-progress, caches or other similar stuff.

This issue has been moved to dart-lang/pub#17.


No LICENSE

Please license your software.

I'd also love it if you could stick a licence in here, thanks!

Having a license on that project is necessary. Thanks for the great work :+1:

To make it really easy I've added a license in pull request #11. Thanks!

Merged PR; thanks everyone


WIP: support setting the clock manually via timeserver attestations

This depends on the branch with the same name in awwad/tuf (Uptane's
TUF fork).  Note that when this is updated after that branch is
merged into develop on awwad/tuf, the dev-requirements.txt change
here should be removed.
This is a work in progress and must be modified before merging.
See also https://github.com/awwad/tuf/pull/22

Coverage increased (+0.02%) to 96.754% when pulling a344463b27f42b98717cb7cbf4299c2cb800a25f on support_time_override into 036451a0e26d712aedd899c0ded3cb74e084d6d6 on develop.

I addressed @lukpueh's comments (refining docstrings -- and renaming a func for good measure).  Thanks, Lukas. 😄
I also added some testing and ran the demo again.  @lukpueh, if you have a second to look over those last two commits added after your review, that'd be appreciated, but I'm merging.


Update dotnet framework version to 5.0

Expected Behavior
Macos and Linux can't use the current required framework version 4.6.2. Compiling a DLL on these systems makes it incompatible with the current Lean codebase.
Actual Behavior
Using an algorithm compiled with dotnet 5.0 should work fine.
Potential Solution
Upgrade the target framework to net50.
Reproducing the Problem
Compile an algorithm in a DLL with dotnet 5.0. Run Lean with it using either the dockerized or compiled versions. Get an error saying the type id can't be found (or something like that, it's on my other computer).
System Information
Macos, dotnet installed with homebrew.
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

[x] I have provided detailed steps to reproduce the issue

I understand this may involve a lot of testing and deployment changes to quantconnect.com so there's for you guys to consider. If this is something that the project wants to do, they someone can use and build upon my PR.

Duplicate of https://github.com/QuantConnect/Lean/issues/452


How to generate rules file?

Hi there!
What's the method to generate an updated rules file for Font Awesome 6?
Thanks!

Hey @AaronSadlerUK ,
This is the solution I came up with:
Follow these instructions on the FA site: https://fontawesome.com/docs/web/setup/host-yourself/webfonts
The configuration for Iconic:

this is the config as json:
{
      "name": "Font Awesome 6 (Brands)",
      "selector": "\\.(fa-[\\w-]+):before {",
      "template": "<i class=\"fa-brands {icon}\"></i>"
}

BUT, there's a problem here. Font Awesome 6 needs 2 CSS files to work: fontawesome.css AND the icon-specific CSS, in this example would be brands.css. Iconic doesn't support configuring two CSS files for one package. So you have two options

Copy the content of fontawesome.css into brands.css
Use the all.css instead. In this case, the regex will be: ".(fa-[\w-]+)::before {" (note the double colon)

The second option will load a pretty big CSS, but you can use the separate files in your frontend, no need to use the all.css
I hope this helps.

Hey Aaron, congrats on your MVP! ;)
Did you manage to configure this? I'll close it for now. Feel free to reopen if needed.

Thanks!
I haven't had a chance to try yet, I'll be sure to update this once I have


InstabugCore is not found

Trying to update from 8.0.0 to 8.0.4
node_modules/instabug-reactnative/ios/InstabugCore.framework: No such file or directory
Indeed, the file does not seem to be there anymore. Do we still need it? The current docs for manual linking still contain this: https://docs.instabug.com/docs/react-native-integration

After removing all mentions of InstabugCore from my xcode build, everything seems to be working fine...

I had no success removing all the references to InstabugCore, reverted to version 8.0.1.

Hey all,
Thanks for reaching out. This issue should be resolved by following the steps here.

Hey, got the same problem and above solution is not working.

Hey @MattyK14 @sebirdman
Were you able to fix the issue?

@Korazy I followed guidelines (unlink and then link) but no success. I have same problem..

@matteodanelli would you be able to tell me which step the error occurs in?

Sure. I've version 2.13.3 and want to upgrade to 8.0.8, the latest.
I've done the following steps:

react-native unlink instabug-reactnative
yarn add instabug-reactnative
react-native link instabug-reactnative
react-native run-ios

And the build fail with the errore Instacore not found.

@matteodanelli Would you be able to give this sample app a go and let me know if you have the same build fail with it?
SampleApp.zip

This works well, but I think the problem is somewhat related to switching from version 2 to version 8.. I even tried to remove instabug completely and installed 8 but seems not works.

@matteodanelli unfortunately we're having a hard time reproducing this issue. Would it be possible to send us a sample app containing this particular bug?

I had a similar issue that I just solved.  The one file I'm assuming is causing you the issue is ios/.xcodeproj/project.pbxproj
Our version of that file had references to InstabugCore.framework.  I don't remember the exact step I did to update that file, but the issue went away after the update.

Thanks. I solved.
I removed every reference of InstabugCore.framework from project.pbxproj.

awesome, im happy to hear that everything is fine now.


Add Virtual Level Plugin

Toggle for virtual level on skill tab
Toggle for virtual total level on skill tab
Toggle for virtual level on Xp Globes
Toggle for virtual level on Hiscores plugin

(Ignore actions left, used ::addxp to set the xp so I "gained" 13m xp in 1 action)

Very smooth, and I like how the total level is untouched by default due to the confusion that might cause. Amazing work.

Unsure why tests are crashing now.. Tried reverting locally and it still gives the same exception.

Have you tried to rebase on upstream master? It looks like it can't even load the base classes.

The tests fail relating to trying to require a plugin as a dependency that happens to be disabled. HiscorePlugin depends on VirtualLevelPlugin and VirtualLevelPlugin is set to not load when outdated, which the tests force. This causes HiscorePlugin to cause the crash since it's attempting to depend on a plugin that isn't loaded. Adam talked about having optional plugins which might fix this problem, along with removing VirtualLevelPlugin#isEnabled().

Looked at Guice, injections, providers and all that.
If you have something dynamic like this, and references are final, I think what you need is a provider that fulfills the interface, but what it gives is a a proxy object. The proxy object would route calls to the plugin when it is on, and when it is not it gives a stub implementation.
This is looking more like a service, or at least, the idea of a service, than a plugin. Not that service is  a realized concept in RuneLite.
A service can be available, or not.
Plugins depending on plugins seems icky to me.

How about a configuration setting to enable the displaying of the levels like 110/110 instead of 99/110?

How about a configuration setting to enable the displaying of the levels like 110/110 instead of 99/110?

I was orig going to do that by default but we (the few others I was talking about this with) couldn't come up with a clean way of handling boosts. Suggestions would be nice. Also, this is blocked by something that I'm not too sure how to do so it might be awhile before this is picked up.

I think a 110/110 approach would sacrifice usability for aesthetics, because the boost level would no longer make any sense.

Could possibly do it how RS3 does, which is showing 110/110 if there were no boosts or anything applied. Otherwise it would show x/99. To me it's just confusing so I don't really know the solution to it.

...I actually like that approach a lot. Maybe we could display it the same way?

Shouldn't be too hard to do. I'll see about rebasing this this weekend maybe and maybe talking to someone about how to avoid the issue I previously ran into. I think the solution Adam brought up was having optional plugins since this PR made it so a few plugins depend on it but it breaks if this plugin is disabled due to not running on outdated client for example.


Update to use newer Spring Boot 2.2

See #231 - we are using Spring Boot 1.5, but should use 2.2 which require some code changes on our side.
Example build error:
[ERROR] /home/travis/build/common-workflow-language/cwlviewer/src/main/java/org/commonwl/view/workflow/WorkflowService.java:[116,34] cannot find symbol
  symbol:   method findOne(java.lang.String)
  location: variable workflowRepository of type org.commonwl.view.workflow.WorkflowRepository

[ERROR] /home/travis/build/common-workflow-language/cwlviewer/src/main/java/org/commonwl/view/workflow/WorkflowService.java:[125,40] cannot find symbol
  symbol:   method findOne(java.lang.String)
  location: variable queuedWorkflowRepository of type org.commonwl.view.workflow.QueuedWorkflowRepository

Fixed in https://github.com/common-workflow-language/cwlviewer/pull/280


Whats the best way to convert the JSON back into a Qlik Sense QVF?

You would have to create the objects back into a qvf file.
Here is a sample project: github.com/mindspank/buildapp

How to convert json to qvf using buildapp?
I tried node buildapp.js <json_file>
It did not work


Planning module stopped in middle of junction turn

Hi team,
VIDEO:
Follow view:
https://drive.google.com/file/d/1LadAKYAvzSF1CsYknMyYqpPmBFYr-FoL/view?usp=sharing
Route Editor Top View:
https://drive.google.com/file/d/1nzX-gZQFE2n0-0hl7RnTo18gcbm3_SQr/view?usp=sharing
Describe the bug
I’ve been trying Apollo 5.0 (LGSVL forked version) out in the San Francisco Map with LGSVL simulator. I discovered some issues, which I think might relate to Apollo's routing, planning and control modules.
In the video, Apollo vehicle is expected to drive from a starting lane to a destination lane, passing a junction inbetween.
The vehicle is spawned near the first point of the starting lane, and the routing destination is set near the last point of the end lane.
All the videos are recorded without any obstacle.
Note that the obstacle perception and traffic light ground truth is fed directly to Apollo.
To Reproduce
Steps to reproduce the behavior:

Set up LGSVL and Apollo 5.0 (forked version) according to LGSVL documentation.
Manually Drive to the starting point shown in the video.
Set destination as shown in the video
Drive a bit forward in the simulator to let Apollo to take over.

Expected behavior
Apollo is expected to turn right at junction J_50.
But in the middle of the turn, Apollo plannning module stopped planning forward.
It seems to be due to that the turn is too sharp for Apollo.
Desktop (please complete the following information):
OS: Ubuntu 1804
Browser Chrome

Seems the road is too narrow for such a sharp turn. Planing leverages lane boundary as a constrain for path generation for most of the scenarios.

@yifeijiang Thanks for your reply.  Shall I close the issue or leave the issues open as a reference?


Can we export these tools to an index.js to embeed with Web requirement

We would like to know the best way to integrate it to an html/js pure website.

Possible duplicate of #31.
It would be needed to create a bundled minified version of the packages needed with Webpack or bundler like that.

Thanks, that will be a duplicated.
The title is not the same but result will.


How to call the non-REST methods?

Right now they are called helpers with the silly description helper : Helpers. RESTful they ain't but useful they ain'tn't..
What would be a good name for that group? Description?

Popular
Simple API

I'm open for suggestions.

main-actions?

Essential API? To express that these methods both represent the main actions as zuphilip suggested and also are the most simple and popular ones as kba suggested.

I like essential. Committed a proposal.

:+1:

essential and advanced should make it clear, like it the way you proposed :+1:

ok then, let's close another one.


Create post 2022-04-20-stuck-with-stock

A bit of CSS this time!

@Syarwin Was this pull request lost? Or if there is something wrong? Thanks!


(SERVER-2859) Add method to revoke multiple certs at once

See usage in https://github.com/puppetlabs/puppetserver/pull/2391

I'd like someone else more familiar with this stuff to also take a look.

@justinstoller is this what you had in mind?


listener macro injection is documented but not released

Adding support for listeners in the store macro was added in March (https://github.com/intendednull/yewdux/pull/52 & https://github.com/intendednull/yewdux/issues/51). The currently live docs/book implies this is a released feature (https://intendednull.github.io/yewdux/persistence.html#additional-listeners), but the latest release 0.9.2 was published in February (https://github.com/intendednull/yewdux/releases/tag/v0.9.2).
Can a new version be released with this feature?

Thanks for bringing this to my attention. Will release soon

Included in 0.9.3 release


build.cmd fails from clean 'git clone'

     Using shared compilation with compiler from directory: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Roslyn
15>MainActivity.cs(9,49): error CS0234: The type or namespace name 'Forms' does not exist in the namespace 'Xamarin' (are you missing an assembly reference?)
    [C:\Users\gd\Documents\Gjallarhorn.Bindable\samples\ElmInspiredOne\Xamarin\ElmInspiredOneXF.Android\ElmInspiredOneXF.Android.csproj]
15>MainActivity.cs(11,33): error CS0115: 'MainActivity.OnCreate(Bundle)': no suitable method found to override [C:\Users\gd\Documents\Gjallarhorn.Bindable\sa
   mples\ElmInspiredOne\Xamarin\ElmInspiredOneXF.Android\ElmInspiredOneXF.Android.csproj]
15>Done Building Project "C:\Users\gd\Documents\Gjallarhorn.Bindable\samples\ElmInspiredOne\Xamarin\ElmInspiredOneXF.Android\ElmInspiredOneXF.Android.csproj"
    (Rebuild target(s)) -- FAILED.
 1>Done Building Project "C:\Users\gd\Documents\Gjallarhorn.Bindable\Gjallarhorn.Bindable.sln" (Rebuild target(s)) -- FAILED.

Build FAILED.
   "C:\Users\gd\Documents\Gjallarhorn.Bindable\Gjallarhorn.Bindable.sln" (Rebuild target) (1) ->
   "C:\Users\gd\Documents\Gjallarhorn.Bindable\samples\ElmInspiredOne\Xamarin\ElmInspiredOneXF.Android\ElmInspiredOneXF.Android.csproj" (Rebuild target) (15)
    ->
   (ResolveAssemblyReferences target) ->
     C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(1988,5): warning MSB3245: Could n
   ot resolve this reference. Could not locate the assembly "Gjallarhorn". Check to make sure the assembly exists on disk. If this reference is required by y
   our code, you may get compilation errors. [C:\Users\gd\Documents\Gjallarhorn.Bindable\samples\ElmInspiredOne\Xamarin\ElmInspiredOneXF.Android\ElmInspiredO
   neXF.Android.csproj]
     C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(1988,5): warning MSB3245: Could n
   ot resolve this reference. Could not locate the assembly "Xamarin.Android.Support.Animated.Vector.Drawable". Check to make sure the assembly exists on dis
   k. If this reference is required by your code, you may get compilation errors. [C:\Users\gd\Documents\Gjallarhorn.Bindable\samples\ElmInspiredOne\Xamarin\
   ElmInspiredOneXF.Android\ElmInspiredOneXF.Android.csproj]
     C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(1988,5): warning MSB3245: Could n
   ot resolve this reference. Could not locate the assembly "Xamarin.Android.Support.Design". Check to make sure the assembly exists on disk. If this referen
   ce is required by your code, you may get compilation errors. [C:\Users\gd\Documents\Gjallarhorn.Bindable\samples\ElmInspiredOne\Xamarin\ElmInspiredOneXF.A
   ndroid\ElmInspiredOneXF.Android.csproj]
     C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(1988,5): warning MSB3245: Could n
   ot resolve this reference. Could not locate the assembly "Xamarin.Android.Support.v4". Check to make sure the assembly exists on disk. If this reference i
   s required by your code, you may get compilation errors. [C:\Users\gd\Documents\Gjallarhorn.Bindable\samples\ElmInspiredOne\Xamarin\ElmInspiredOneXF.Andro
   id\ElmInspiredOneXF.Android.csproj]
     C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(1988,5): warning MSB3245: Could n
   ot resolve this reference. Could not locate the assembly "Xamarin.Android.Support.v7.AppCompat". Check to make sure the assembly exists on disk. If this r
   eference is required by your code, you may get compilation errors. [C:\Users\gd\Documents\Gjallarhorn.Bindable\samples\ElmInspiredOne\Xamarin\ElmInspiredO
   neXF.Android\ElmInspiredOneXF.Android.csproj]
     C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(1988,5): warning MSB3245: Could n
   ot resolve this reference. Could not locate the assembly "Xamarin.Android.Support.v7.CardView". Check to make sure the assembly exists on disk. If this re
   ference is required by your code, you may get compilation errors. [C:\Users\gd\Documents\Gjallarhorn.Bindable\samples\ElmInspiredOne\Xamarin\ElmInspiredOn
   eXF.Android\ElmInspiredOneXF.Android.csproj]
     C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(1988,5): warning MSB3245: Could n
   ot resolve this reference. Could not locate the assembly "Xamarin.Android.Support.v7.MediaRouter". Check to make sure the assembly exists on disk. If this
    reference is required by your code, you may get compilation errors. [C:\Users\gd\Documents\Gjallarhorn.Bindable\samples\ElmInspiredOne\Xamarin\ElmInspire
   dOneXF.Android\ElmInspiredOneXF.Android.csproj]
     C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(1988,5): warning MSB3245: Could n
   ot resolve this reference. Could not locate the assembly "Xamarin.Android.Support.v7.RecyclerView". Check to make sure the assembly exists on disk. If thi
   s reference is required by your code, you may get compilation errors. [C:\Users\gd\Documents\Gjallarhorn.Bindable\samples\ElmInspiredOne\Xamarin\ElmInspir
   edOneXF.Android\ElmInspiredOneXF.Android.csproj]
     C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(1988,5): warning MSB3245: Could n
   ot resolve this reference. Could not locate the assembly "Xamarin.Android.Support.Vector.Drawable". Check to make sure the assembly exists on disk. If thi
   s reference is required by your code, you may get compilation errors. [C:\Users\gd\Documents\Gjallarhorn.Bindable\samples\ElmInspiredOne\Xamarin\ElmInspir
   edOneXF.Android\ElmInspiredOneXF.Android.csproj]
     C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(1988,5): warning MSB3245: Could n
   ot resolve this reference. Could not locate the assembly "FormsViewGroup". Check to make sure the assembly exists on disk. If this reference is required b
   y your code, you may get compilation errors. [C:\Users\gd\Documents\Gjallarhorn.Bindable\samples\ElmInspiredOne\Xamarin\ElmInspiredOneXF.Android\ElmInspir
   edOneXF.Android.csproj]
     C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(1988,5): warning MSB3245: Could n
   ot resolve this reference. Could not locate the assembly "Xamarin.Forms.Core". Check to make sure the assembly exists on disk. If this reference is requir
   ed by your code, you may get compilation errors. [C:\Users\gd\Documents\Gjallarhorn.Bindable\samples\ElmInspiredOne\Xamarin\ElmInspiredOneXF.Android\ElmIn
   spiredOneXF.Android.csproj]
     C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(1988,5): warning MSB3245: Could n
   ot resolve this reference. Could not locate the assembly "Xamarin.Forms.Platform". Check to make sure the assembly exists on disk. If this reference is re
   quired by your code, you may get compilation errors. [C:\Users\gd\Documents\Gjallarhorn.Bindable\samples\ElmInspiredOne\Xamarin\ElmInspiredOneXF.Android\E
   lmInspiredOneXF.Android.csproj]
     C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(1988,5): warning MSB3245: Could n
   ot resolve this reference. Could not locate the assembly "Xamarin.Forms.Platform.Android". Check to make sure the assembly exists on disk. If this referen
   ce is required by your code, you may get compilation errors. [C:\Users\gd\Documents\Gjallarhorn.Bindable\samples\ElmInspiredOne\Xamarin\ElmInspiredOneXF.A
   ndroid\ElmInspiredOneXF.Android.csproj]
     C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(1988,5): warning MSB3245: Could n
   ot resolve this reference. Could not locate the assembly "Xamarin.Forms.Xaml". Check to make sure the assembly exists on disk. If this reference is requir
   ed by your code, you may get compilation errors. [C:\Users\gd\Documents\Gjallarhorn.Bindable\samples\ElmInspiredOne\Xamarin\ElmInspiredOneXF.Android\ElmIn
   spiredOneXF.Android.csproj]

   "C:\Users\gd\Documents\Gjallarhorn.Bindable\Gjallarhorn.Bindable.sln" (Rebuild target) (1) ->
   "C:\Users\gd\Documents\Gjallarhorn.Bindable\samples\ElmInspiredOne\Xamarin\ElmInspiredOneXF.Android\ElmInspiredOneXF.Android.csproj" (Rebuild target) (15)
    ->
   (CoreCompile target) ->
     MainActivity.cs(9,49): error CS0234: The type or namespace name 'Forms' does not exist in the namespace 'Xamarin' (are you missing an assembly reference
   ?) [C:\Users\gd\Documents\Gjallarhorn.Bindable\samples\ElmInspiredOne\Xamarin\ElmInspiredOneXF.Android\ElmInspiredOneXF.Android.csproj]
     MainActivity.cs(11,33): error CS0115: 'MainActivity.OnCreate(Bundle)': no suitable method found to override [C:\Users\gd\Documents\Gjallarhorn.Bindable\
   samples\ElmInspiredOne\Xamarin\ElmInspiredOneXF.Android\ElmInspiredOneXF.Android.csproj]

14 Warning(s)
2 Error(s)

Time Elapsed 00:00:54.70
Running build failed.
Error:
Building C:\Users\gd\Documents\Gjallarhorn.Bindable\Gjallarhorn.Bindable.sln failed with exitcode 1.

Build Time Report
Target         Duration

Clean          00:00:00.0063960
AssemblyInfo   00:00:00.1145980
Build          Failure
Total:         00:00:57.5485069
Status:        Failure

Building C:\Users\gd\Documents\Gjallarhorn.Bindable\Gjallarhorn.Bindable.sln failed with exitcode 1.
CS0234: MainActivity.cs(9,49): The type or namespace name 'Forms' does not exist in the namespace 'Xamarin' (are you missing an assembly reference?)
CS0115: MainActivity.cs(11,33): 'MainActivity.OnCreate(Bundle)': no suitable method found to override

This looks like you're getting errors compiling the Xamarin projects. Do you have the full Xamarin tools installed for VS 2017?


DL4J/ND4J QA: Memory leak detection system

In recent testing, we found what it looks like a memory leak has slipped through testing into the 1.0.0-beta4 release.
To prevent future issues like this, we should set up a system to run a set of tests for say 2-6 hours - for example, continually calling training on a complex DL4J or SameDiff net. It should be automated, dockerized, etc.
This would be run infrequently, perhaps once every 2 weeks, and then again once before release.
It would detect memory leaks in the following way:

By seeing if an OOM is thrown after some number of hours of runtime
By checking if memory is continually growing over time (i.e., ensure memory use is stable over the long term)

Of course, coverage is important here - we might need to design some nets (DL4J and SameDiff) that use as many different layers as possible.

hi,
I am using beta5 and regular crashes.
dl4j-memory-crash-dump-1573031192830_32.txt
does this helP ?

@stubbi59 Please open a separate issue with your full network configuration
this issue isn't the place to be asking for help, it's unrelated to your problem


 Doesn't actually crash on Windows 8 and Windows 10. I haven't tried it on Windows 7 though.

Have you check the updates on your machine? Microsoft has corrected the bug.

Le 4 mai 2016 à 09:22, whateverburps<EMAIL_ADDRESS>a écrit :
Script not working, just spams a bunch of links in the powershell window. Doesn't actually crash on Windows 8 and Windows 10. I haven't tried it on Windows 7 though.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub


Add course choices gcse requirements row and component

Context
In order to give better guidance to candidates applying for courses we need better contextual prompts if they do not meet course requirements. We need to be able to let candidate know if they have pending GCSE's where they are not accepted.
Changes proposed in this pull request
Component has three states of content.
accept_pending_gcse == true

accept_pending_gcse == false or nil

accept_pending_gcse == false or nil and candidate has pending gcses

Guidance to review
Link to Trello card
https://trello.com/c/pmS8NaDt/3840-📐dev-apply-indicate-when-a-course-has-gcse-requirements-that-the-candidate-doesnt-meet
Things to check

[x] This code does not rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] API release notes have been updated if necessary
[x] Required environment variables have been updated added to the Azure KeyVault

Will give it a proper review in the morning George, but other than a couple of nits this is looking really really good.


Dereference unique_ptr that is NULL on osx_86-64 in the CI

Getting the following error in some runs of the CI, not all of them. Results to reproduce this locally using export OSX_BUILD_ARCH=x86_64 and running the tests have been unsuccessful.
Link to failed build
================================================================================
Query unexpectedly failed (/Users/runner/work/community-extensions/community-extensions/test/sql/scalar/local_clustering_coefficient.test:131)
================================================================================
select a.id, a.name, local_clustering_coefficient from local_clustering_coefficient(pg, student, know), student a where a.id = lcc.id;
================================================================================
Actual result:
INTERNAL Error: Attempted to dereference unique_ptr that is NULL!
This error signals an assertion failure within DuckDB. This usually occurs due to unexpected conditions or errors in the program's logic.
For more information, see https://duckdb.org/docs/dev/internal_errors

Seems to happen during this test:
CREATE TABLE Student(id BIGINT, name VARCHAR);INSERT INTO Student VALUES (0, 'Daniel'), (1, 'Tavneet'), (2, 'Gabor'), (3, 'Peter'), (4, 'David');

CREATE TABLE know(src BIGINT, dst BIGINT, createDate BIGINT);INSERT INTO know VALUES (0,1, 10), (0,2, 11), (0,3, 12), (3,0, 13), (1,2, 14), (1,3, 15), (2,3, 16), (4,3, 17);

CREATE TABLE Foo(id BIGINT);INSERT INTO Foo VALUES (0), (1), (2), (3), (4);

-CREATE PROPERTY GRAPH pg
VERTEX TABLES (
    Student,
    Foo
    )
EDGE TABLES (
    know    SOURCE KEY ( src ) REFERENCES Student ( id )
            DESTINATION KEY ( dst ) REFERENCES Student ( id )
    );

select a.id, a.name, local_clustering_coefficient from local_clustering_coefficient(pg, student, know), student a where a.id = lcc.id;

I could use jewels09 or jewels08 but unable to access those at the moment.

Unable to reproduce. Will close for now but see if it pops up in the CI again


Show errors

(Includes #1124 because of potential merge conflicts)
This is 3 separate pieces that have 3 commits associated with them:

Show an error when config.json isn't present
Provide mechanisms to show errors if one of the ajax calls loading data fails
Show the user an error when a query fails (this uses a separate mechanism to ensure that it's placed in a semantically meaningful way... a query that fails is something like foo==bar)

Oops, forgot to lint.

ps great work!

config.json
When config.json is missing, it's a completely blank screen, with text to the effect of
Error loading config.json: server error (Bad Gateway)

The rationale for this is that the mechanism for showing the entire UI relies on config.json, so if it's not there then loading the UI doesn't make sense. Typically you only run into this with a misconfiguration anyways -- but right now, you get a blank page, which is confusing. This is better than a blank page.
This can be triggered by running npm run dev without launching a zipkin query server.
ajax errors
Screenshot for bad gateway (this can be triggered by runnning npm run dev without launching a zipkin server, just make sure to add a {} to static/config.json so you don't trigger the config.json error instead).

query errors
Screenshot for bad query such as foo==bar... the error message could be better if the query server returned a better message. That's something for a future PR.

:thumbsup:

needs a rebase, then ready to go

Oops, thought I had done that. Here you go.

Great work!
Maybe the only thing missing, that we should add, is to catch exceptions in traceToMustache.js, so that any bugs in my sloppy JavaScript code will be shown with a stack trace, instead of rendering a black page :stuck_out_tongue:

pink is the new black, I guess


Tt 1602 artifactory

I build https://build.ida.digital.cabinet-office.gov.uk/job/ida-msa/668/ from this branch. Looks green, so let's :shipit:


Security issue in ansi-regex dependency (via yargs)

Currently it is impossible to install showdown without pulling in a security vulnerability, because showdown has a tightly versioned dependency on yargs which pulls in a vulnerable ansi-regex.
The security advisory is:
https://github.com/advisories/GHSA-93q8-gq69-wqmw

@jlaine I updated yargs on the master branch. Eventually there will be a 2.0.0 release with this fix.

@SyntaxRules Can this be updated to a new version of the showdown package as well?

@code-by-gijs For sure, I'm trying to work through as much of the backlog I can before releasing- as you can tell there are quite a few issues. It may take a bit before I can get the release out.

@SyntaxRules awesome, thanks!

With some ambitious plans, it looks like the 2.0.0 release could be quite a ways away.  Might we be able to just apply the above commits on the last release tag and publish a patch update that handles the vulnerabilities / audit failures before then?

I should also mention that's something I'm willing to do if you want to have me on with the right permissions. I'm also a maintainer on the much more widely used Winston logger for similar reasons.

Even without permissions, I can offer this quickest path route:
This is the commit which fixes the issue, but it's quite a ways ahead of the last release, so I can understand reluctance to do a release from that.
However, the version_1.x branch is only one tiny commit ahead of the release, and a brief inspection demonstrates that's not going to break anything important.
The simplest PR would be to add the caret on the yargs line on the version_1.x branch and do a patch-level release from that.

I've added a PR which should fix this.  It drops support for node v6 and v8, so technically it should probably go out as 2.0.0, with the next big breaking release now being planned going out in n months as 3.0.0.
This commit bumps the version number and adds changelog notes you can copy (the source of) that and paste it right into the release notes.
Merge, release on Github, publish to npm, and this issue is solved.  Thanks for your work!


Brownie complaints of package depedendencies

When doing pip install -r requirements.txt in the regular README steps, I get several ERRORs:
...
Requirement already satisfied: setuptools in ./venv/lib/python3.8/site-packages (from jsonschema==3.2.0->eth-brownie->-r requirements.txt (line 8)) (44.0.0)
ERROR: eth-brownie 1.18.1 has requirement black==22.1.0, but you'll have black 21.11b1 which is incompatible.
ERROR: eth-brownie 1.18.1 has requirement click==8.0.3, but you'll have click 8.0.4 which is incompatible.
ERROR: eth-brownie 1.18.1 has requirement platformdirs==2.4.1, but you'll have platformdirs 2.4.0 which is incompatible.
ERROR: eth-brownie 1.18.1 has requirement pytest==6.2.5, but you'll have pytest 7.1.1 which is incompatible.
ERROR: eth-brownie 1.18.1 has requirement tomli==2.0.0, but you'll have tomli 1.2.2 which is incompatible.
ERROR: eth-brownie 1.18.1 has requirement typing-extensions==4.0.1, but you'll have typing-extensions <IP_ADDRESS> which is incompatible.
Installing collected packages: regex, ...

Fixed in commit https://github.com/tokenspice/tokenspice/commit/951cf85403e95d5c58448250cc2ecb35b3be5d17


[FR] Supporting Hover Editor and/or Open In New Window

Hi! I love this plugin, very useful.
Could you consider adding support for Page Preview(Obsidian) / Hover Editor(Plugint) like when holding Ctrl and move over the button, show the preview:

Or, could you add right-click menu to open the page in new window (and other ways)?

Hi, thanks for the feedback. I have added a context menu to the navbar, so you can pick where to open the files. I have also added an item here to copy the Obsidian URL, as that was easy to do.
There are also now settings for picking the default behaviour on how to open them.
If you have more ideas for features, and/or things that can go in the context menu, then you are welcome to create more issues :)
I tried looking at Hover Editor plugin, or just adding markdown preview on hover, but that might take some time for me to get right. I don't know if Hover Editor has an API, so other developers can use it, but I will look into it.
You can see the new version with context menu here:
https://github.com/karstenpedersen/obsidian-daily-note-navbar/releases/tag/0.1.7

Hi, thanks for the feedback. I have added a context menu to the navbar, so you can pick where to open the files. I have also added an item here to copy the Obsidian URL, as that was easy to do.
There are also now settings for picking the default behaviour on how to open them.
If you have more ideas for features, and/or things that can go in the context menu, then you are welcome to create more issues :)
I tried looking at Hover Editor plugin, or just adding markdown preview on hover, but that might take some time for me to get right. I don't know if Hover Editor has an API, so other developers can use it, but I will look into it.
You can see the new version with context menu here: https://github.com/karstenpedersen/obsidian-daily-note-navbar/releases/tag/0.1.7

Thank you for developing so quickly, this is a pleasant surprise!  :D
I've updated to new version and it works great!
For now the Middle Mouse Button would also trigger the context menu (same with Right Mouse Button), maybe changing it to Open in new tab would be more consistency with native link operation?

As for the Hover Editor, I guess it would just override the Obsidian's native preview feature. 🤔
So maybe just supporting Page Preview and the plugin itself would do the other things (I hope so, haha)

I am now using Obsidians ModEvents, so you can now press Ctrl+click or middle mouse button for new tab. You can also press Ctrl+shift+alt+click to open them in windows, or Ctr+alt+click to open in split. The context menu is now only opened with the right mouse button.
The normal clicks behaviour can still be changed in the settings tab.

I will wait a bit with the preview, as I first want to make the navbars responsive, so they only show dates that fit on the screen.

I am now using Obsidians ModEvents, so you can now press Ctrl+click or middle mouse button for new tab. You can also press Ctrl+shift+alt+click to open them in windows, or Ctr+alt+click to open in split. The context menu is now only opened with the right mouse button.
The normal clicks behaviour can still be changed in the settings tab.
https://github.com/karstenpedersen/obsidian-daily-note-navbar/releases/tag/0.1.9
I will wait a bit with the preview, as I first want to make the navbars responsive, so they only show dates that fit on the screen.

Wow that's amazing, thanks!


add support for GCS (similar to what exists for S3)

Thanks for submitting your feedback to Dockstore.
Please fill in the appropriate section depending on whether you want to submit a feature request or a bug report.
Feature Request
in reading the Dockstore paper the other day, I saw mention of support for input and output files coming from and going to S3 -- I'd like to request similar support for Google Cloud Storage (GCS)
Desired behaviour
Bug Report
Expected behaviour
Actual behaviour
Steps to reproduce the behaviour
(Attach tool/workflow documents or links where applicable to help us reproduce your issue)
Environment (Browser or OS and Dockstore version)
Describe your operating system (relevant for CLI and launcher) or your web browser (name and version, relevant for the Dockstore website)
┆Issue is synchronized with this JIRA Story
┆Sprint: Lighthouse Sprint 38 Lorrette
┆Issue Number: DOCK-56

@smrgit Public data available on GCS such as "http://storage.googleapis.com/uspto-pair/applications/05900002.zip" already works without a file provisioning plugin.  For private data, is there a preferred method of authentication that you want to be supported?

@garyluu -- that's great to know thanks -- for data requiring credentials, maybe using the same approach that htslib recently implemented  would make sense?

The best approach to auth would be to support service account credentials, as I think htslib did. Service accounts are the recommended way, according to Google security experts.
As a convenience so users can get started easily, it's good to also support user account credentials, though it's advisable to alert users to the caveats and provide documentation. The recommendation is that if you use user credentials, you should do so from your own cloud project, which no other users have access to, or from your own computer, which no other users have access to.

➤ Walt Shands commented:
The GCS plugin is working but needs some cleanup and tests to be written.
https://github.com/dockstore/gs-plugin/tree/feature/issue-601-gs-plugin

➤ Walt Shands commented:
Unit tests implemented
PR https://github.com/dockstore/gs-plugin/pull/1 submitted and under review.

➤ Walt Shands commented:
PR accepted and merged

➤ Walt Shands commented:
The plugin support service account credentials. The USER just needs to point the environment variable GOOGLE_APPLICATION_CREDENTIALS to the file with the service account key before using the Dockstore command line. A link to Google instructions for setting this up is provided in the GCS plugin READ.ME

This ticket needs to be verified.

➤ Charles Overbeck commented:
Verified by using the workflow at https://staging.dockstore.org/workflows/github.com/DataBiosphere/topmed-workflows/UM_aligner_wdl:1.32.0?tab=files ( https://staging.dockstore.org/workflows/github.com/DataBiosphere/topmed-workflows/UM_aligner_wdl:1.32.0?tab=files ).
Downloaded the test parameter JSON file from that same workflow. That file has https URLs; I changed them to to gs urls by changing https to gs and removing storage.googleapis.com ( http://storage.googleapis.com ). For example,  https://storage.googleapis.com/topmed_workflow_testing/topmed_aligner/input_files/NWD176325.25rea ( https://storage.googleapis.com/topmed_workflow_testing/topmed_aligner/input_files/NWD176325.25rea )ds.cram becomes gs://topmed_workflow_testing/topmed_aligner/input_files/NWD176325.25reads.cram.
Tested against staging with 1.6.0-beta.4.
Did notice an issue downloading plugins while testing, but it is unrelated to this fix. Logged it as https://github.com/ga4gh/dockstore/issues/2261 ( https://github.com/ga4gh/dockstore/issues/2261 )

There's a notable download speed discrepancy between gs and https paths, gs is about 2-3x slower. #2268


[Mesheryctl] Error coming in version.go (server_spec_handler)

Signed-off-by: Chadha93<EMAIL_ADDRESS>Description
After making the required changes in the server_spec_handler and error. go, an error automatically gets raised in the version. go (CheckLatestVersion not declared by package handlers)
This PR fixes #3305
Notes for Reviewers
This is only for server_sepc_handler
Signed commits

[x] Yes, I signed my commits.

@dhruv0000 @sayantan1413 Could you please suggest some changes for server_spec_handler.

Uh-oh... a conflict.

Heads-up: Merge conflict - https://github.com/meshery/meshery/pull/3411/conflicts

@dhruv0000 I have changed it accordingly but there is again an error coming in version.go regarding checkLatestVersion not declared. Me and @sayantan1413 also re-checked it but we are not using CheckLatestVersion anywhere in server_spec_handlers.go now

@dhruv0000 I have changed it accordingly but there is again an error coming in version.go regarding checkLatestVersion not declared. Me and @sayantan1413 also re-checked it but we are not using CheckLatestVersion anywhere in server_spec_handlers.go now

I guess I explained it wrong. Let me try again. I suggested that, since,

CheckLatestVersion was used as a generic function so lets not convert it into a handler method,
and function is using logger to print info on the version data it's returning, so
you can move this two logs outside the function (and not create it as a handler method) and print them in ServerVersionHandler and checkMesheryctlClientVersion (FYI they are the methods that called the CheckLatestVersion function, I didn't want you to rename CheckLatestVersion to checkMesheryctlClientVersion ).

if res.Outdated {
		logrus.Info("\n  ", serverVersion, " is not the latest Meshery release. Update to v", res.Current, ". Run `mesheryctl system update`")
		h.log.Info(serverVersion, " is not the latest Meshery release. Update to v", res.Current, ". Run `mesheryctl system update`")
	}

	// If user is running the latest release, let them know.
	if res.Latest {
		logrus.Info("\n  ", serverVersion, " is the latest Meshery release.")
		h.log.Info(serverVersion, " is the latest Meshery release.")
	}

Poke me if you are still confused.

Contention - https://github.com/meshery/meshery/pull/3411/conflicts (of course, @dhruv0000 pointed it out faster that I could).


chore: disable preview banner dismissal

Suggestion from @eladb to disable the ability to dismiss the preview banner - so that no one forgets.

Is this really necessary? If a user dismisses this and forgets, it's on them. It only stays closed for the duration of their session anyways (i.e until their construct hub tabs are closed)

@gabewomble definitely not really necessary - we just floated this and figured i'd make a PR that we can agree/disagree based on what the team thinks.

It only stays closed for the duration of their session anyways (i.e until their construct hub tabs are closed)

Cool, for some reason I thought its persisted across sessions.
I'm leaning towards keeping it as is, wondering what other people think though.

Team decided against this for now


Extend aws s3 binding

Description
I added the folowing operations:

get
delete
copy

Issue reference
Please reference the issue this PR will close:  #538
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[ ] Created/updated tests
[x] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#1479

@mukundansundar comments are fixed

@pkedy Can you review it?

@vikborisov We are in the middle of our v1.2 release but we will review this soon.  Thanks!

@vikborisov please see the linter fails: https://github.com/dapr/components-contrib/pull/869/checks?check_run_id=2679162365

@vikborisov please resolve the conflicts and look at the Files changed tab to see the linter issues that need to get fixed. Once that's done we can merge.
Thanks!

ping @vikborisov

ping @vikborisov

@vikborisov there also needs to be a docs PR for this

Closing in favor of https://github.com/dapr/components-contrib/pull/1081


[Error] Downloading stash for Standard, details logged to DebugInfo.log

What's the solution for this problem?

The new version of Procurement is out, which fixes this issue: https://github.com/Stickymaddness/Procurement/releases/tag/1.9.6
Unfortunately until GGG decide to support the dev community, these type of issues will continue to happen as it is out of our hands. http://i.imgur.com/yrPtajM.jpg


Cores per subscription vs. VM total cores per region

It is said that the Cores per subscription maximum limit is 10,000. After looking at the VM total cores per region maximum limit (Resource Manager), though not specified, I believed that this limit would never be higher than the subscription limit. However, I have a customer which has currently a soft limit for Total Regional vCPUs (Resource Manager) much higher than 10,000. How's this possible? Is anything wrong/unclear with the documentation?

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

ID: 1cd57b6d-3c6f-e546-b3ea-f83892f4c23d
Version Independent ID: 27aecc7b-f107-96d4-b044-ae026bca2727
Content
Content Source
Service: billing

@helderpinto Thank you for the valuable feedback. I forwarded your feedback to the content team.

@helderpinto Thank you for the feedback. I'm looking into this now.

#in-process

@helderpinto I apologize for the delay, but we're still investigating this question. Thank you for your patience!

@helderpinto Hello, again, apologies for the delay. We've been having an internal discussion about your question. I think there might be a confusion between the two tables. The first "Subscrition limits" table refers to the old classic deployment model, so that is the only place that we list 10,000 cores as a maximum limit. The Resource Manager table, as you mentioned, says contact support. But conceivably that number could be higher. This is true even is you have the maximum 10,000 VMs per region, because each VM could use multiple cores. With this said, the actual limit is up to Azure when you contact them to perform an increase. But I think the confusion is around the classic versus resource manager limits in this one case. I'm going to close this issue, but if this doesn't make sense, or if you think I'm missing something, please add more information to this issue and we'll keep discussing. I do think we could try to make the article more clear on this, and I'll enter a work item.
Thank you, again, for the feedback, and apologies (again) for the long wait.
#please-close

@helderpinto We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion

@helderpinto That's a great point. In this case, we should list it in both tables if the answer is "contact support" for cores per subscription for resource manager. Thank you.


Wrong gradients with C API?

The following program performs a forward + backward pass on the sum of two length-1 vectors (via the elemwise_add operator)
#include <iostream>

#include "mxnet/c_api.h"
#include "nnvm/c_api.h"

#define checkedMXCall(func, ...)                              \
  {                                                           \
    if (func(__VA_ARGS__) != 0) {                             \
      printf("MX call %s failed at line %d:\n%s",             \
            #func, __LINE__, MXGetLastError());               \
      exit(1)               ;                                 \
    }                                                         \
  }

int main() {

  /* Create symbol */
  const char json[] = "{\"nodes\": [{\"op\":\"null\",\"name\":\".Inputs.Input1\",\"inputs\":[]},{\"op\":\"null\",\"name\":\".Inputs.Input2\",\"inputs\":[]},{\"op\":\"elemwise_add\",\"name\":\".$0\",\"inputs\":[[0,0,0],[1,0,0]]},{\"op\":\"_copy\",\"name\":\".Outputs.Output\",\"inputs\":[[2,0,0]]}],\"arg_nodes\":[0,1],\"heads\":[[3,0,0]]}";
  SymbolHandle sym;
  checkedMXCall(MXSymbolCreateFromJSON, json, &sym);

  /* Create NDArray for arguments */
  int dev_type = 1;
  int dev_id = 0;
  mx_uint shape[1] = {1};
  void *data;
  NDArrayHandle in_arr_1, in_arr_2;
  checkedMXCall(MXNDArrayCreate, shape, 1, dev_type, dev_id, 0, 0, &in_arr_1);
  checkedMXCall(MXNDArrayCreate, shape, 1, dev_type, dev_id, 0, 0, &in_arr_2);
  checkedMXCall(MXNDArrayGetData, in_arr_1, &data);
  /* Set values for arguments */
  *reinterpret_cast<float*>(data) = 0.4;
  checkedMXCall(MXNDArrayGetData, in_arr_2, &data);
  *reinterpret_cast<float*>(data) = 0.5;

  /* Create NDArray for gradients */
  NDArrayHandle grad_arr_1, grad_arr_2;
  checkedMXCall(MXNDArrayCreate, shape, 1, dev_type, dev_id, 0, 0, &grad_arr_1);
  checkedMXCall(MXNDArrayCreate, shape, 1, dev_type, dev_id, 0, 0, &grad_arr_2);
  /* Set values for gradients */
  checkedMXCall(MXNDArrayGetData, grad_arr_1, &data);
  *reinterpret_cast<float*>(data) = 0;
  checkedMXCall(MXNDArrayGetData, grad_arr_2, &data);
  *reinterpret_cast<float*>(data) = 0;
  /* Attach gradients to arguments */
  uint32_t grad_req_1[1] = {1};
  uint32_t grad_req_2[1] = {1};
  checkedMXCall(MXAutogradMarkVariables, 1, &in_arr_1, grad_req_1, &grad_arr_1);
  checkedMXCall(MXAutogradMarkVariables, 1, &in_arr_2, grad_req_2, &grad_arr_2);

  /* Create cached op */
  const char *cachedop_keys[1] = {"static_alloc"};
  const char *cachedop_vals[1] = {"true"};
  CachedOpHandle cached_op;
  checkedMXCall(MXCreateCachedOp, sym, 1, cachedop_keys, cachedop_vals, &cached_op, false);

  /* Set autograd to record & set training mode */
  int dummy_prev;
  checkedMXCall(MXAutogradSetIsRecording, 1, &dummy_prev);
  checkedMXCall(MXAutogradSetIsTraining, 1, &dummy_prev);

  /* Run forward */
  int n_outs;
  NDArrayHandle *out_arr_p = nullptr;
  const int *dummy_stypes = nullptr;
  NDArrayHandle inputs[] = {in_arr_1, in_arr_2};
  checkedMXCall(MXInvokeCachedOp, cached_op, 2, inputs, dev_type, dev_id, &n_outs, &out_arr_p, &dummy_stypes);
  checkedMXCall(MXNDArrayWaitToRead, *out_arr_p);

  /* Create NDArray for outgrad */
  NDArrayHandle outgrad_arr;
  checkedMXCall(MXNDArrayCreate, shape, 1, dev_type, dev_id, 0, 0, &outgrad_arr);
  /* Set values for outgrad */
  checkedMXCall(MXNDArrayGetData, outgrad_arr, &data);
  *reinterpret_cast<float*>(data) = 1;

  /* Run backward */
  checkedMXCall(MXAutogradBackward, 1, out_arr_p, &outgrad_arr, false);
  checkedMXCall(MXNDArrayWaitToRead, grad_arr_1);
  checkedMXCall(MXNDArrayWaitToRead, grad_arr_2);

  /* Check results */
  checkedMXCall(MXNDArrayGetData, in_arr_1, &data);
  std::cout << "INPUT 1: " << *reinterpret_cast<float*>(data) << "\n";
  checkedMXCall(MXNDArrayGetData, in_arr_2, &data);
  std::cout << "INPUT 2: " << *reinterpret_cast<float*>(data) << "\n";
  checkedMXCall(MXNDArrayGetData, *out_arr_p, &data);
  std::cout << "OUTPUT: " << *reinterpret_cast<float*>(data) << "\n";
  checkedMXCall(MXNDArrayGetData, outgrad_arr, &data);
  std::cout << "OUTGRAD: " << *reinterpret_cast<float*>(data) << "\n";
  checkedMXCall(MXNDArrayGetData, grad_arr_1, &data);
  std::cout << "GRAD 1: " << *reinterpret_cast<float*>(data) << "\n";
  checkedMXCall(MXNDArrayGetData, grad_arr_2, &data);
  std::cout << "GRAD 2: " << *reinterpret_cast<float*>(data) << "\n";

  return 0;
}

It behaves as expected, producing
INPUT 1: 0.4
INPUT 2: 0.5
OUTPUT: 0.9
OUTGRAD: 1
GRAD 1: 1
GRAD 2: 1

Switching off the gradient request for the second input, i.e. defining the grad_req arrays as
  uint32_t grad_req_1[1] = {1};
  uint32_t grad_req_2[1] = {0};

also behaves as expected, producing 0 for GRAD 2 (gradient arrays are initialized with 0):
INPUT 1: 0.4
INPUT 2: 0.5
OUTPUT: 0.9
OUTGRAD: 1
GRAD 1: 1
GRAD 2: 0

But switching off the first gradient with
  uint32_t grad_req_1[1] = {0};
  uint32_t grad_req_2[1] = {1};

seems to switch off both GRAD 1 and GRAD 2!
INPUT 1: 0.4
INPUT 2: 0.5
OUTPUT: 0.9
OUTGRAD: 1
GRAD 1: 0
GRAD 2: 0

I must be doing something wrong here, because the equivalent python example works just fine with gradient requests 0 and 1 ('null' and 'write'):
import mxnet as mx

json = "{\"nodes\": [{\"op\":\"null\",\"name\":\".Inputs.Input1\",\"inputs\":[]},{\"op\":\"null\",\"name\":\".Inputs.Input2\",\"inputs\":[]},{\"op\":\"elemwise_add\",\"name\":\".$0\",\"inputs\":[[0,0,0],[1,0,0]]},{\"op\":\"_copy\",\"name\":\".Outputs.Output\",\"inputs\":[[2,0,0]]}],\"arg_nodes\":[0,1],\"heads\":[[3,0,0]]}"
sym = mx.symbol.fromjson(json)

ex = sym._bind(
	mx.cpu(),
	{'.Inputs.Input1': mx.nd.array([0.4]), '.Inputs.Input2': mx.nd.array([0.5])},
	args_grad={
		'.Inputs.Input1': mx.ndarray.zeros((1)),
		'.Inputs.Input2': mx.ndarray.zeros((1))
	},
	grad_req={'.Inputs.Input1': 'null', '.Inputs.Input2': 'write'}
)
ex.forward(is_train=True)
print(ex.outputs)
ex.backward(out_grads=mx.nd.array([1]))
print(ex.grad_arrays)

[
[0.9]
<NDArray 1 @cpu(0)>]
[None,
[1.]
<NDArray 1 @cpu(0)>]

Can anyone spot the problem with the C program with gradient requests 0 and 1?

Any help on this?

Analysis:
The issue is solved mainly by comparing  elemwise_add with  elemwise_mul at operation registration.  @barry-jin  pointed out an important discrepancy between these two operators today. The discrepancy is in “registering the function for creating the node of the operator in a backward pass”:
https://github.com/apache/incubator-mxnet/blob/da4ff3a4dc0bd6a54af3d75c492021d18ba1867b/src/operator/tensor/elemwise_binary_op_basic.cc#L111 https://github.com/apache/incubator-mxnet/blob/da4ff3a4dc0bd6a54af3d75c492021d18ba1867b/src/operator/tensor/elemwise_binary_op_basic.cc#L238
elemwise_mul uses ElemwiseGradUseIn, since calculation of _back_mul depends on input value. However,  elemwise_add uses CloneGradient, the reason of which is not clear yet. But  ElemwiseGradUseNone is another valid option for elemwise_add . So I tested it by replacing  CloneGradient  with ElemwiseGradUseNone .
Result:
The issue is solved! ./demo2 0 1 specifies the gradient request as following, and 2021 is the hardcoding head gradient.
 uint32_t grad_req_1[1] = {0};
 uint32_t grad_req_2[1] = {1};

$~/mxnet/issue2/build2$ ./demo2 0 1
[19:45:23] ../src/nnvm/legacy_json_util.cc:209: Loading symbol saved by previous version v0.8.0. Attempting to upgrade...
[19:45:23] ../src/nnvm/legacy_json_util.cc:217: Symbol successfully upgraded!
[19:45:23] ../src/engine/engine.cc:55: MXNet start using engine: NaiveEngine
[19:45:23] ../src/storage/storage.cc:199: Using Pooled (Naive) StorageManager for CPU
INPUT 1: 0.4
INPUT 2: 0.5
OUTPUT: 0.9
OUTGRAD: 2021
GRAD 1: 0
GRAD 2: 2021

$~/mxnet/issue2/build2$ ./demo2 1 0
[19:49:59] ../src/nnvm/legacy_json_util.cc:209: Loading symbol saved by previous version v0.8.0. Attempting to upgrade...
[19:49:59] ../src/nnvm/legacy_json_util.cc:217: Symbol successfully upgraded!
[19:49:59] ../src/engine/engine.cc:55: MXNet start using engine: NaiveEngine
[19:49:59] ../src/storage/storage.cc:199: Using Pooled (Naive) StorageManager for CPU
INPUT 1: 0.4
INPUT 2: 0.5
OUTPUT: 0.9
OUTGRAD: 2021
GRAD 1: 2021
GRAD 2: 0

$~/mxnet/issue2/build2$ ./demo2 1 1
[19:50:11] ../src/nnvm/legacy_json_util.cc:209: Loading symbol saved by previous version v0.8.0. Attempting to upgrade...
[19:50:11] ../src/nnvm/legacy_json_util.cc:217: Symbol successfully upgraded!
[19:50:11] ../src/engine/engine.cc:55: MXNet start using engine: NaiveEngine
[19:50:11] ../src/storage/storage.cc:199: Using Pooled (Naive) StorageManager for CPU
INPUT 1: 0.4
INPUT 2: 0.5
OUTPUT: 0.9
OUTGRAD: 2021
GRAD 1: 2021
GRAD 2: 2021

Further investigation:
This result shows CloneGradient   is the most possible reason that causes this issue. So the remaining check is

In bug report , the sym is built by:

1. {
        "nodes": [
            {
                \"op\":\"null\",
                \"name\":\".Inputs.Input1\",
                \"inputs\":[]
            },
            {
                \"op\":\"null\",
                \"name\":\".Inputs.Input2\",
                \"inputs\":[]
            },
            {
                \"op\":\"elemwise_add\",
                \"name\":\".$0\",
                \"inputs\":[[0,0,0],[1,0,0]]
            },
            {
                \"op\":\"_copy\",
                \"name\":\".Outputs.Output\",
                \"inputs\":[[2,0,0]]
            }
        ],
        \"arg_nodes\":[0,1],
        \"heads\":[[3,0,0]]
    }

It is possible that "_copy" operation intrigues  this issue in CloneGradient. This helps understand why it fails.

Other usages of CloneGradient in mxnet\src\operator\contrib\stes_op.cc

CloneGradient{"_backward_round_ste"}
CloneGradient{"_backward_sign_ste"}

It is possible they have the similar bug.

@KexinFeng thanks for looking into this!
It is possible that "_copy" operation intrigues this issue in CloneGradient. This helps understand why it fails.

There must be other factors besides this because the equivalent python example in my original report works fine and it also has the _copy operator. This also mean that there is a particular combination of C API calls (the one used by python) which is able to work around this bug.

I see.

because the equivalent python example in my original report works fine and it also has the _copy operator
Actually I notice a discrepancy between the python call and cpp call. In python code,  it calls CachedOp::Forward() and then CachedOp::StaticForward(). In cpp code, CachedOp::Forward() calls CachedOp::DynamicForward().  I currently don't know if this discrepancy triggers the bug. But it can be tested quicly by setting something like hybridize(static_alloc=True) on python, or setting static_alloc=False on cpp.

Unfortunately dynamic allocation is not an option for me, at least for now.
Anyway, I have verified that static_alloc = false indeed fixes the issue. It also explains why it works on python, because no flag is passed to the cached op from python and static_alloc is false by default. Hardcoding  flags = {"static_alloc": "true"} here exposes the issue in the python script as well.
Thanks for submitting the PR.

@szha @leezu @sandeep-krishnamurthy Bringing this issue to your attention - this issue is most probably a bug in the handling of reqs in CachedOp when static_alloc is set to True, which seems pretty major. Could you assign somebody to take a look?

I don't think the root cause is in CachedOp. As I was debugging this issue, the elemwise_add is using CloneGradient, which means copy ograds multiple times for the inputs.
For cached_op, if the static_alloc is on, then it will set backward graph with grad_graph outputs
https://github.com/apache/incubator-mxnet/blob/3480ba2c6df02bb907d3a975d354efa8697c4e71/src/imperative/cached_op.cc#L270-L281
In the case of elemwise_add(a, b), the grad_graph will be like this.

The gradient of b will be the copy of the gradient of a. So there will be divergence between (case1: a.grad_req = null, b.grad_req = write) and (case2: a.grad_req = write, b.grad_req = null) when constructing the new graph based on the grad_graph.
From my point of view, the solution of this bug is to change the elemwise_add gradient function to this
.set_attr<nnvm::FGradient>("FGradient",
  [](const nnvm::ObjectPtr& n, const std::vector<nnvm::NodeEntry>& ograds) {
    std::vector<nnvm::NodeEntry> ret;
    const size_t input_count = n->inputs.size();
    ret.reserve(input_count);
    for (size_t i = 0; i < input_count; ++i) {
      ret.emplace_back(MakeNode("ones_like", n->attrs.name + "_grad_ones", {n->inputs[i]}, nullptr, &n));
    }
    return ret;
});

@KexinFeng FYI

The graph is exactly the same, whether you have static or dynamic alloc. The problem I believe lies here:
https://github.com/apache/incubator-mxnet/blob/3480ba2c6df02bb907d3a975d354efa8697c4e71/src/imperative/cached_op.cc#L986-L1006
especially lines 992 and 1002 - it sets the reqs for NodeEntries of the graph outputs based on the user preferences. This is only fine if those NodeEntries are not actually used in the other places in the computation, which for most cases is true. However, the  gradient of elementwise_add is just a split. The CloneGradient method does not do any copying actually, it just reuses the NodeEntry and passes it to both downstream operators - this is the right behavior. But then when 1 of those downstream places is the output of the graph marked with req=null, you get a problem - because of those lines in StaticBackward function that edge is marked as kNullOp even though it is used in the rest of the computation.
The proper fix therefore would be to change the logic in the StaticBackward to take into account all usages of those NodeEntries and only mark it as null if the graph output is the only usage. There could also be an additional improvement here (although the real world impact of this is probably pretty minimal) to make the kNullOp requirement "traverse" the graph - right now if you have a chain of (single input/output) operations A -> B -> C which ultimately produces unnecessary output, then only the C operation will know about this and A and B will be performed (and their outputs allocated) no matter what.

Also, you definitely do not want to make gradient of add be ones_like ;-).


Code sample for "Populate a CarouselView with data" section doesn't work

The code sample provided under "Populate a CarouselView with data" is a poor example, and fails to render a CarouselView.
An updated version might look something like:
    <CarouselView>
        <CarouselView.ItemsSource>
            <x:Array Type="{x:Type x:String}">
                <x:String>Baboon</x:String>
                <x:String>Capuchin Monkey</x:String>
                <x:String>Blue Monkey</x:String>
                <x:String>Squirrel Monkey</x:String>
                <x:String>Golden Lion Tamarin</x:String>
                <x:String>Howler Monkey</x:String>
                <x:String>Japanese Macaque</x:String>
            </x:Array>
        </CarouselView.ItemsSource>
        <CarouselView.ItemTemplate>
            <DataTemplate>
                <Label Text="{Binding .}"/>
            </DataTemplate>
        </CarouselView.ItemTemplate>
    </CarouselView>

The screenshots also do not reflect what the code would actually render, with regard to formatting/layout, which can be misleading to users.

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

ID: b99d7746-543f-8608-25f3-f5c9b2fb8b0d
Version Independent ID: c53cec53-1432-d7ee-0694-d66044986156
Content: Xamarin.Forms CarouselView Data - Xamarin
Content Source: docs/xamarin-forms/user-interface/carouselview/populate-data.md
Product: xamarin
Technology: xamarin-forms
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Hi @rachelkang
It's too problematic expecting the control to behave the same in subsequent releases, so I've removed this example (which did render content, in an ugly way, on iOS and Android for me without using a template).


fix: ignore RUSTSEC-2024-0370

Summary
Ignore RustSec warning.
Background
We get a non-critical warning when running cargo audit: RUSTSEC-2024-0370.
When running cargo tree -i -p=proc-macro-error we can see that proc-macro-error is a dependency of borsh which is already at the latest version.
Given that the RustSec report doesn't suggest any concrete problems with proc-macro-error and how difficult it will be to move away from this dependency, I have just ignored this warning in CI.
Changes

Ignore RustSec warning in .cargo/audit.toml.
Also fixed a typo causing a compiler warning.

Testing
Ran cargo audit locally.

I suppose we should make an issue over at borsh?

There's an issue logged here which would resolve this.


WIP Fixes lots of bugs

As per #16 we need to fix several things, this PR is those fixes

[x] #15 - Firefox issues
[x] #12 - Reactions conflict
[x] #20 - Edit poll problem
[x] #9 - i18n
[x] #19 - Improve style of polls

PR is finished, awaiting code review

@CDK2020 Do you have some screenshots?

@PartialDevAdmin
https://imgur.com/a/qmlgJB0

@CDK2020 I am unable to access imgur, can you share an image directly?

@PartialDevAdmin

@datitisev Looks good! I am going to clone the repo locally and test it out, will report back then!


Fixing JSON structure with LLM itself

Testing this approach to fix the JSON with another LLM call. This approach can be better but I'm just testing this as of now.

made pr on main repo by mistake.

@sc-govsin did this work?

@penguine-ip  for some LLMs it does (Mixtral), for some it doesn't (Command R).

Still there is small need of modification, I'll create a new PR once I complete the testing with few more LLMs.


Initial ResetOffset Webhook

Subtask of #588 to provide optional support for ResetOffset CRDs in the existing KafkaChannel Webhook.
Proposed Changes

🎁  Add check in webhook main.go for new Env Var indicating support for ResetOffset.
🎁  Add utility function to Webhook to add the ResetOffset CRD to the types map.
🎁  Add new ClusterRole for ResetOffset Webhook for future ClusterRoleBinding of Webhook.
🎁  Add copy of existing webhook-deployment.yaml including ResetOffset Env Var.

Notes

The ResetOffset support is still "inactive" and has not been added to any Channels/Sources/etc.
To enable it the following will need to be done...

Link the webhook-deployment-ro.yaml instead of the existing webhook-deployment.yaml
Link the webhook-clusterrole.yamland add section to webhook clusterrolebinding yaml

Release Note
Release Notes will be provided near the end of the ResetOffset feature development.
Docs
Documentation will be provided near the end of the ResetOffset feature development.
Hold for review...
/hold

/lgtm

/unhold


[Kuma] Need custom sizing for tabbed editor

For the interactive editor we need to add a few custom CSS style rules to the Kuma code base. The following page can be used for testing.
https://developer.mozilla.org/en-US/docs/User:wbamberg/HTML_editor_user_test_pages/datalist

Acceptance Criteria
Custom classes added and merged into Kuma codebase.

PR: https://github.com/mozilla/kuma/pull/4842


ban commnand

!ban comand ir not working

The bot listens to the ban command in-game, there is no !ban command in discord.


Update unit tests

This PR:

updates CircleCI config to test across multiple Python versions (3.9-3.12)

Note: only runs coveralls on Python 3.12

removes unnecessary imports in cli/__main__.py

Ensures all type hints are compatible with Python 3.9

updates loading entrypoints for Python 3.12, fixes #607

re-orders environment.yml so that packages are in the correct section and listed alphabetically

:exclamation: marks all tests in test_temporal_interpolate.py as "long" to prevent them from running in CI due to #611

Updates sentineleof to version 9 or greater

this means orbits will be downloaded from ESA CDSE, which will require credentials
sentineleof also now returns paths instead of strings, so _get_acq_time_from_gunw_id and tests were updated accordingly

Adds an ensure_orbit_credentials function in prepFromGUNW.py to ensure ESA CDSE credentials are in ~/.netrc or provided via environment variables
Note: For this one, I wanted to put this in models/credentials.py so all credentials were handled in the same place, but everything there is related to acquiring weather models so it didn't make sense to stuff it in there without a significant refactor.

Adds a setup_from_env function to models/credentials.py which will pull all credentials needed for acquiring weather model data from environment variables and ensure the correct config file is written. This makes setting up credentials in CI pipelines significantly easier.
Note: This could also have a command line interface, but I couldn't decide if it was worth it.

@dbekaert the checks will pass once the ESA_CDSE_USERNAME and ESA_CDSE_PASSWORD environment variables are added to CircleCI so that orbits can be downloaded.
I also decided to not use GitHub Actions as CircleCI handles forks better. You can remove the repository secrets I had you add earlier.

@dbekaert the checks will pass once the ESA_USERNAME and ESA_PASSWORD environment variables are added to CircleCI so that orbits can be downloaded.

Done


Package doesn't show up in Package Control listing

Hey, is this project still active? It's not showing up in any listings on the Package Control website.

It's not maintained anymore because I'm not using Haxe at the moment. I'm not sure if I ever submitted it to Package Control. It's a very simple project though, feel free to clone it if you need to make changes :)


This commit adds a score configuration option to the package

This commit adds a new configuration option to the package, allowing developers to set the minimum score required for a successful verification. By default, the score is set to 0.5, but developers can now adjust this value to better suit their specific use case.

Nice job, the 0.5 default seems also to be recommended by Google: https://developers.google.com/recaptcha/docs/v3#interpreting_the_score
I think currently without this fix, this package is rendered useless because it basically only verifies that the user loaded the reCAPTCHA script.


Need to be able to pull headers out of the restlib response

Some downstream systems send response headers as well as a body. We want to be able to markup the sysl to say which header fields are wanted as well as the body

There's a workaround to solve this issue.

@ChloePlanet which is?

Hi Andrew and the team,
Thanks for the confirmation this afternoon, just want to put in more info for the team to reference. :)
So, one of the downstream will response error 400 for different scenarios for business:
400 - Bad Request
{
  "message": [
    {
      "text": "10001 - Business Error AAA",
      "type": "error"
    }
  ]
}

400 - Bad Request
{
  "message": [
    {
      "text": "10002 - Business Error BBB",
      "type": "error"
    }
  ]
}

What we need to achieve here, is to get the error body and drill down into the "text" part to see what is the actual cause for this 400 error.
Cheers,
Ping

Hi @suipinglu , I'm running bah-bff to test this issue, could you help give me an example endpoint to reproduce the 400 response?


[FLINK-24182][task] Do not interrupt tasks/operators that are already closing

Otherwise if we interrupt operator that is doing a blocking call to release
some resources in closing, we can cause those resources to leak. A good example
is Kafka sink, which wants to abort transactions in close() method
Verifying this change
This change adds a couple of new tests to cover for the new behaviour.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Just a quick note: Could you split 4a39348 into the new change and a revert commit?

Just a quick note: Could you split 4a39348 into the new change and a revert commit?

I think that's not easily do-able, as the code has changed. I have split this commit into two parts, by extracting the changes that remove Future<Void> from the return type of cancel() method, which was the bulk of the changes in this commit.

Could we move the initial commits in range 40e48c9d1bcd90a671f1572b55c5bdf445e1950f..7504cd9aae82a742cab6e5dd15bbbf4ab49b3599 to a separate PR (just to make sure they compile and run) and merge them already? I reviewed those and they look good, but they distract from the actual change.

Sure, done: https://github.com/apache/flink/pull/17328


Allow for configurable disabling of the automatic pageView event.

This should fix #92 and #93.
The JS changes are minor, but we should run the SauceLabs tests nonetheless. Will merge only after success there.

SauceLabs test are without regression. Merging.


Add JustPeek in Force Touch

Project URL
https://github.com/justeat/JustPeek
Description
JustPeek is an iOS Library that adds support for Force Touch-like Peek and Pop interactions on devices that do not natively support this kind of interaction.
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 or later
[x] Supports Swift 3
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Error

:no_entry_sign:
Found 1 link issue

Link issue by awesome_bot

Line
Status
Link

758
301
https://github.com/ideaismobile/IDMPhotoBrowser redirects tohttps://github.com/thiagoperes/IDMPhotoBrowser

  Generated by :no_entry_sign: danger

Hey @naeemshaikh90, you're on 🔥🔥🔥🔥!


Feature/151 standardize code review recipes

Updated all recipe docs (except python) to conform to a common standard - Python is changed in #150
Update all links for CSE and other links to work after change in  PR #148
Remove TypeScript recipe as we already have a JavaScript/TypeScript recipe and moved the relevant parts into the JavaScript recipe

TODO: this is not verifying or updating technical content - this will be updated in a series of other issues.  This is to move the existing content to a consistent format

I have merged in PR #148 that is already accepted in order to avoid merge conflicts later
This PR concerns files under the recipes folder


Add visitor methods to Config in prost-build

The type_attribute, field_attribute is powerful but sometimes constraining. Previously, identifying enums vs messages was impossible due to this (see: https://github.com/tokio-rs/prost/pull/784). There are other customer-specific patterns that can't be turned into '*_attribute' methods.
I believe a type_visitor and field_visitor (and maybe message_visitor, enum_visitor) method should be added to Config. Then customers can do something like
     config.type_visitor("path.to.package", |ty, buf| {
         if(ty.name.endswith("GRPC") {
             buf.push_str("#[serde(rename_all = \"camelCase\")]");
         }
    });

I did some research on implementation details in https://github.com/tokio-rs/prost/issues/586
Thanks!

This is a really interesting idea! I think its a bit complicated and exposes a lot of internal details so I am not sure if its the right approach. Would be interesting to see a comparison on how other languages handle similar sort of features for their code gen.

Regarding other languages: in a sense, Prost is 'compiling' (or transpiling) the proto to Rust. The visitor pattern is pretty common in compilers, in general.
In terms of internals: I was just reusing the pattern used in the *_attribute methods. For the lambda input, the DescriptorProto types are already publicly externalized via prost_types. For output, instead, the lambda can be expected to return an Option(String), Some(X) if it wants to append an attribute. So instead, something like
     config.type_visitor("path.to.package", |ty| {
         if(ty.name.endswith("GRPC") {
             return Some("#[serde(rename_all = \"camelCase\")]");
         }
         None
    });

In retrospect, this is much cleaner than passing a buf parameter.
WIth that a _visitor method could potentially be created for each kind of DescriptorProto in prost_types (message, field, enum, file, method, oneof, service).


Accept external CFLAGS

Some distributions build the programs with a specific set of CFLAGS.
Lets allow that by adding raylibs flags.

Thanks @jubalh! Please, could you push this commit to develop branch?

Sure, one second. I'll close this PR.

New PR  is: https://github.com/raysan5/raylib/pull/295


[Bug] Error fetching models?

The following code:
import { pipeline } from "@xenova/transformers";

let pipe = await pipeline(
  "text-generation",
  "EleutherAI/gpt-neo"
);
let result = await pipe("Write me a love poem about cheese.", {
  do_sample: false,
  max_new_tokens: 200,
  no_repeat_ngram_size: 3,
  temperature: 0.9,
  repetition_penalty: 2.0,
});

console.log(result);

Produces:
node .\main.js
file:///C:/Users/ares/Github/xxx/test/node_modules/@xenova/transformers/src/utils/hub.js:223
            throw Error(`Could not locate file: "${remoteURL}".`)
                  ^

Error: Could not locate file: "https://huggingface.co/nlptown/EleutherAI/gpt-neo/resolve/main/onnx/model_quantized.onnx".
    at handleError (file:///C:/Users/ares/Github/xxx/test/node_modules/@xenova/transformers/src/utils/hub.js:223:19)
    at getModelFile (file:///C:/Users/ares/Github/xxx/test/node_modules/@xenova/transformers/src/utils/hub.js:412:24)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async constructSession (file:///C:/Users/ares/Github/xxx/test/node_modules/@xenova/transformers/src/models.js:88:18)
    at async Promise.all (index 1)
    at async AutoModelForSequenceClassification.loadModel [as LOAD_FUNCTION] (file:///C:/Users/ares/Github/xxx/test/node_modules/@xenova/transformers/src/models.js:280:16)
    at async AutoModelForSequenceClassification.from_pretrained (file:///C:/Users/ares/Github/xxx/test/node_modules/@xenova/transformers/src/models.js:2591:20)
    at async Promise.all (index 1)
    at async pipeline (file:///C:/Users/ares/Github/xxx/test/node_modules/@xenova/transformers/src/pipelines.js:1462:17)
    at async file:///C:/Users/ares/Github/xxx/test/main.js:3:12

Node.js v20.1.0

I tried many different ONNX-based model from Hugging Face but resulting to the same error.

I reckon the issue is with the path the library is looking for, for example with optimum/gpt2, the correct path should be:

https://huggingface.co/optimum/gpt2/blob/main/tokenizer.json

But it seems that the hardcoded path uses resolve/main instead of blob, see:

Error: Could not locate file: "https://huggingface.co/optimum/gpt2/resolve/main/tokenizer_config.json".

Hi there. This is because the repos you are attempting to use don't contain ONNX weights in a folder called "onnx". Once web-ready models become more popular, hopefully more models will support it.
Fortunately, it's really simple to convert your own models using the conversion script (which uses Optimum behind the scenes). See the docs for more info.
To help users get started, I've already converted a lot of models, which can be found by searching on the hub: https://huggingface.co/models?other=transformers.js
In your case, you're trying to load gpt-neo, which I haven't yet converted, but I have converted the 125M version of it: https://huggingface.co/Xenova/gpt-neo-125M
So, you can do:
let pipe = await pipeline(
  "text-generation",
  "Xenova/gpt-neo-125M"
);

Hope this helps.

Closing the issue for now, but feel free to ask any further questions 👍

Thanks for the reply @xenova but I assumed that any ONNX-based model would work, meaning any of these models:

https://huggingface.co/models?library=onnx&sort=downloads

Did I get that wrong?

Thanks for taking the time to answer my questions. 😊


DatePicker: monthSpinner not working

Thanks for your project! I was looking for a simple DatePicker, and this seems to be a nice one :-)
But: the monthSpinner in the popup does not work. It seems, that the text of spinner's textField cannot be selected.
Can be reproduced with DateTimePickerTest

Thanks, I will take a look. In the meantime, could you update your PR to use spaces instead of tabs?

I ran the date picker test with your updates, and everything appears to work OK. However, the text of the spinner is still not selectable - I'm not sure what behavior you were expecting.
Either way, I think this is a good fix to apply because it resolves the focus issue you mentioned in the PR.

Thanks for your comments.
I understood, you want to keep the focus at the textfield. I know, that the spinner usually works on the selected part of the text, so it could also increment/decrement the year if selected. But moving the focus to the spinner would break the general behaviour to open the popup, whenever the textfield gets the focus. You could add a button (like in comboboxes) to open the popup. But automatic closing is very difficult then. And this approach might conflict with other pickers, like TimePicker, which do not use editable elements.
I suggest to keep it this way.
I'll prepare the requested changes when I'm back on my machine on monday.

This change has been merged to master.

This has been released. @folkfreund thank you for your help!