Server-side HTTPs requests to API fail: 'sslv3 alert handshake failure'

I'm building a Nuxt application utilising server-side rendering and a Vuex connecting to an external API.  I want to fill my store with some data on application start - on (re)load basically - right now it only fetches data when you navigate to one of the pages using the internal links of the application. SSR isn't working as well.
So I'm trying to use nuxtServerInit in index.js (I'm using Vuex modules) and dispatch an action to one of my store modules. The axios request causes an error however: SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure, this error doesn't occur when axios does the same request from the client-side.
I think I've narrowed it down to this node https issue. When I run a plain Node https request from nuxtServerInit I get the error, but when I append 'ecdhCurve' : 'auto' to the request options the request resolves normally. Is it possible to configure Nuxt to automatically append the option to all https request of my application, or is that bad practice and is the API server I'm connecting to at fault here?
This fails:
    const request = https.get({
      hostname: 'api.example.com',
      path: '/my/endpoint'
    })

This works:
    const request = https.get({
      hostname: 'api.example.com',
      path: '/my/endpoint',
      ecdhCurve: 'auto'
    })

I'm running Node v9.6.1 (Homebrew version, but it fails on a Linux box as well with v9.5.0) and Nuxt 1.4.0.

I've been poking around in the configuration of the API server and changed the ssl_ecdh_curve value of nginx to prime256v1 instead of secp384r1 and requests now go through properly and SSR is working. Using secp521r1 also works, so I'm not really sure what's going on here.

If client isn't affected, you might want to do
const tls = require('tls')
tls.DEFAULT_ECDH_CURVE = 'auto'

somewhere, for example in server.js (your file) or even at the top of nuxt.config.js.
This will only affect the server module and not go to the client at all.
Regarding security, as far as I understood the 8.x.x release accidentally shipped a strict setting for curves (but not the most secure one), and they can't change the default until 10.x.x because of LTS/semver reasons.
In 10.x.x it is 'auto' so I doubt that's a very insecure option.


[FLINK-10553] [sql] Unified sink and source table name in SQL statement

What is the purpose of the change
This pull request solves a bug in flink SQL statement, in which sink table name in INSERT INTO clause can only be enclosed in back-ticks. The sink table name should be consisted with source table name in FROM clause.
Verifying this change
This change is already covered by existing tests, such as ExternalCatalogInsertTest#testBatchSQL, ExternalCatalogInsertTest#testStreamSQL.
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, Yarn/Mesos, 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)

Hi Jerry,
Thanks for fixing this. Your changes seems good. However, I have a side question: do we expect that the external catalog understands the notation of "catalog.db.table", that's is, three level hierarchy, or it just take the table name literally. From InMemoryExternalCatalog, it seems to me the catalog doesn't seem doing anything interpretation on the given table name. I'm not sure if I missed anything. (Nothing wrong about your changes, but just about my understanding.)
Thanks,
Xuefu


Creating Chemistry Metapackage

Currently, the Chemistry package adds reference to two dlls form two different projects:

DataModel: with the C# classes required to parse broombridge files and create the necessary Q# structures.
Runtime: With the Q# code to run the actual simulations
Having a single nuget package makes it hard to break dependencies and to reprlace package with project references for the right environment.
This change creates a nuget package for each project, and converts the Microsoft.Quantum.Chemistry package to a metapackage that simply refers the other two.

 It looks like the main source of conflict is adding the conversion tool, so let me revise that manually and update this PR. Thanks for your patience.

My apologies, @anpaz-msft, I accidentally pushed a commit past the merge conflict resolution.


feat!: add @vitest/coverage-v8 package

Adds new coverage provider package @vitest/coverage-v8. For end-users it should provide identical coverage results as @vitest/coverage-c8.

This package does not implement the coverage options excludeNodeModules, allowExternal and src. I think we can implement these if needed, but at the moment even the @vitest/coverage-istanbul doesn't have these.

Adds deprecation warning to @vitest/coverage-c8. This package is still around but will be removed in future breaking-change releases.

Migration
npm uninstall @vitest/coverage-c8
npm install --save-dev @vitest/coverage-v8

// vitest.config.ts
export default defineConfig({
  test: {
    coverage: {
-      provider: 'c8'
+      provider: 'v8'

Motivation for new package
The @vitest/coverage-c8 has always had to utilize some private APIs of c8. This has been required since c8 isn't really intended for libraries as it's rather for standalone usage. Non-breaking changes in c8 like https://github.com/bcoe/c8/pull/469 can break @vitest/coverage-c8 without major version bumps.
The @vitest/coverage-c8 is using c8 only for merging, processing and converting the V8 coverage reports, and for creating the final reports. Code instrumentation moved from expensive process.env.NODE_V8_COVERAGE to node:inspector usage already in #2786.
Now with @vitest/coverage-v8 we don't use c8 package at all. New dependencies compared to @vitest/coverage-c8 are added to preserve the functionality:

bunch of istanbul packages to process coverage results and create reports. Same packages are used by @vitest/coverage-istanbul already.
@bcoe/v8-coverage for merging V8 coverage reports - this package is also used by c8 and jest
v8-to-istanbul for converting the coverage reports from V8 to istanbul format

Enables (or at least makes it easier to implement) https://github.com/vitest-dev/vitest/issues/3251 as now we have more control over c8.
BREAKING CHANGES:

@vitest/coverage-istanbul requires latest vitest version. Some utilities were moved to vitest package for sharing them with the new v8 provider.

Next steps
Once this PR is released we can:

Remove @vitest/coverage-c8 package completely. The old releases will still remain in NPM registry. Latest release has deprecation warning in place.
Remove all mentions of c8 from documentation
Make provider: 'v8' the default option

Testing:
Compare results between existing @vitest/coverage-c8 and the new @vitest/coverage-v8.

[x] test/coverage-test
[x] test/workspaces
Manual testing with third party projects:

[x] zustand: 100% coverage match
[x] vuejs/core: 99% coverage match. Some conditional T extends U types are not considered as branches anymore. Earlier we didn't pass source maps for files containing only typings (not sure why), and let c8 resolve the source map. Now we correctly pass the source map from vite-node.
[x] netlify/cli: 100% coverage match

Does the package name @vitest/coverage-c8 make any sense anymore? Maybe @vitest/coverage-v8 instead?

@AriPerkkio if changed, @vitest/coverage-c8 will be depreciated at first right?

Moved all changes of @vitest/coverage-c8 package to new package @vitest/coverage-v8 instead. This PR does not remove anything c8 related - it only adds a deprecation warning message to @vitest/coverage-c8 initializer.
Small breaking change in @vitest/coverage-istanbul which now requires latest vitest version.

Thanks for the description, it's neat 💯

Package @vitest/coverage-v8 does not work correctly in terms of coverage for sure. Package @vitest/coverage-c8 is more accurate - sees all uncovered and skiped areas in Vue templates, takes into account missing test files and overall coverage.
Other things being equal settings, package @vitest/coverage-v8 simply always passes the tests and never outputs missing lines or coverage problems.
So for now, these are not interchangeable packages. I rolled back to package @vitest/coverage-c8.

@aleksi-magner these two packages should have 100% identical output. We've had some issues with Vue's coverage before so there might be something that we are missing in the new package as well. Please file a bug report with reproduction case and let's fix that.


feat(specs): refactor and add new tests to model inheritance

split inheritance test cases into 4 sub test cases
and test cases for single discriminator and enum discriminator

resolve #379
Cadl Ranch Contribution Checklist:

[x] I have written a scenario spec
[x] I have meaningful @scenario names. Someone can look at the list of scenarios and understand what I'm covering.
[x] I have written a mock API
[x] I have used @scenarioDocs for extra scenario description and to tell people how to pass my mock api check.

@timotheeguerin I've adopted your comments. List of changes:

add getMissingDiscriminator and getWrongDiscriminator case to enum discriminator tests
refactor non-discriminator scenario

rename scenario to not-discriminated
change response type from OkResponse to NoContentResponse

fix return type of put operations in multiple scenario
refactor scenario multiple-discriminator

rename to nested-discriminator
improve Shark declaration

add test case for legacy way of defining base model in single-discriminator scenario


GUI doesn't expand properly

When the amount of items in the GUI is exactly a row, it doesn't expand properly

Has been fixed and will be in v1.6.4 update

Yay badbones XD


Can't use mouse

Efficiency issue: Observation box function example: start typing in the observation name and you get 7 choices that are close to what you want. We used to be able to use the mouse to select the one you want. If you use the mouse, there is no acceptance of the choice; now you have to use the keyboard to scroll down to the observation you want for it to "take".

This is a duplicate of #30.  The mouse click issue is a known bug in JavaFX. Closing this issue as the details are captured in the duplicate.


Remove .DS_Store

Protip: such files (as well as files specific to a given IDE) should be a part of your global git ignore. Otherwise, local .gitignore becomes a global list of not-so-important files for every possible OS and IDE.

Nice!


Add VersionsManager 1.1.5

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if adding a new cask:

[x] Named the cask according to the token reference.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.
[x] Checked there are no open pull requests for the same cask.
[x] Checked the cask was not already refused in closed issues.
[x] Checked the cask is submitted to the correct repo.

@core-code How many apps are you planning to add to Cask?

3 - 5 more

Can you commit to keeping them updated?

not really, time is short :/
but 4 of the apps are quite stable and shouldn't see any updates anyway.
the other ones could be added with "version :latest" since we follow a strict download version numbering scheme anyway and also have download symlinks that always point to the latest version.

not really, time is short :/

Adding Casks that no one is using and expecting someone else to maintain them is not cool.

the other ones could be added with "version :latest" since we follow a strict download version numbering scheme anyway and also have download symlinks that always point to the latest version.

No, if versioned download are available then the Casks should be versioned.

i've spent time to make the caskfiles as a service to your users, if you think thats not cool please don't add them
if you change your mind here are 3 more https://pastebin.com/MEvyNvrH


IDE keep showing "Reload Now" popup at launch

Hello,
I just started to use platformIO on mac OS X. I keep getting popup whenever I launch the IDE. It says Installing IDE... and after completion, there is option to Reload Now.
After choosing "Reload Now", it agains tries installing IDE and show option to Reload Now. This keeps happening and I can only get out of it if I choose , Reload later. I am guess this is not a normal behavior.  Any workaround ?

I see it. Sorry. Give me a few minutes.

Please sorry for that issue:

Please click on "Reload Later"
Then click on gear icon on PlatformIO IDE Toolbar which will open Atom's Settings
Then go to Settings > Packages and upgrade PlatformIO IDE to 1.0.4.
Restart IDE

That was fast!
I have followed the steps and the popup is no longer coming after reloading.
Thanks


Fix for deserialization errors while decoding Option[T] from empty responses

This PR is aimed to fix #161

Released in 1.4.1


Logging

Why are these changes needed?

Enables the capability tracking each request to llm api and the response, the telemetry will be saved in sqlite db.

Related issue number
#7
TODO:

[ ] track cost in db
[ ] track session id
[ ] pass in db name as argument
[ ] command line arg to enable logging
[ ] option to dump logging to console
[ ] error handling
[ ] update doc
[ ] tests
[ ] versioning db schema?

Checks

[ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[ ] I've made sure all auto checks have passed.

Codecov Report
Attention: 43 lines in your changes are missing coverage. Please review.

Comparison is base (1508f53) 30.82% compared to head (5e5c20b) 18.74%.
Report is 3 commits behind head on main.

Files
Patch %
Lines

autogen/oai/telemetry.py
34.61%
34 Missing :warning:

autogen/oai/client.py
35.71%
9 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1146       +/-   ##
===========================================
- Coverage   30.82%   18.74%   -12.08%
===========================================
  Files          30       31        +1
  Lines        4033     4107       +74
  Branches      915      981       +66
===========================================
- Hits         1243      770      -473
- Misses       2711     3254      +543
- Partials       79       83        +4

Flag
Coverage Δ

unittests
18.74% <34.84%> (-12.03%)
:arrow_down:

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

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

Hi all. I'm resurrecting this PR, since instrumentation is perhaps the next big missing piece of AutoGenBench. Stay tuned.

I think it might be worthwhile looking into standard solutions for telemetry. One open standard for collecting data is OpenTelemetry, which is supported by a range of open and close source solutions such as honeycomb.io and Prometheus.

I looked at OpenTelemetry earlier, and it seemed a little heavyweight -- but maybe our needs have evolved to warrant that. We definitely need something

I agree with having a lightweight local implementation such as this. For any kind of server deployment, we need a standard solution like OpenTelemetry. I might make a follow up PR with this very soon.

I agree with having a lightweight local implementation such as this. For any kind of server deployment, we need a standard solution like OpenTelemetry. I might make a follow up PR with this very soon.

My only unmovable requirement is that it support a range of metrics computations in AutoGenBench.

[ ] move session id to start logging
[ ] return session id

Separate PR:

expose the agent id - what if I only want to see the data related to assistant agent/user proxy agent?
add agent id to log completion

@cheng-tan there is a test error in open ai test.

thanks @ekzhu, it only happens on the ci working on fixing it


question about fast run

Hi,
The waymo dataset is too large. Is it possible to run the code without downloading the waymo dataset, e.g., a lightweight demo? (I only want to know the implementation details about the code so that I can better use it, e.g., input and output shape of each function.)
Best,

Yes, you could download a single waymo data file here.
After that we could provide a pretrianed model.

Yes, you could download a single waymo data file here. After that we could provide a pretrianed model.

Thank you for you reply! But the 'download' button on your provided website is gray and can not be clicked. Dont know specifically how to download this file. Is there download link from google drive etc?
Best,

You could refer to the individual files in this page

You could refer to the individual files in this page

Thanks. The individual file can be downloaded after registration.
Next, should I process the individual file following the same procedure as in mmdetection3d?

I recommend to follow their documents but use the code in this repo to process the data, due to official MMDet3D update the coordinates system.

I recommend to follow their documents but use the code in this repo to process the data, due to official MMDet3D update the coordinates system.

Thanks. The mini-dataset has been ready by little modification on the data converter script. Well, where should I get the pre-trained checkpoint then? (If I have not miss something in README.md.)
Best,

Just give me your email and I will send you a private link.

@., thanks!
-----Original Messages-----
From:"Lue Fan" @.>
Sent Time:2022-10-10 07:51:30 (Monday)
To: tusen-ai/SST @.>
Cc: "Xiao Pan" @.>, Author @.***>
Subject: Re: [tusen-ai/SST] question about fast run (Issue #75)
Just give me your email and I will send you a private link.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Could you show me the email at this page? The email address will be blocked if you reply via email.

Could you show me the email at this page? The email address will be blocked if you reply via email.
<EMAIL_ADDRESS>Thank!

I have sent you the link.

I have sent you the link

Appreciated!


shell command path not showing in VS code

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

The "shell command" path is not showing up in the search in the VS code app. I've uninstalled, reinstalled the app, restarted my computer. VS code is in my applications folder.

.

@SkiSherpa What exactly are you trying to accomplish?  If you want to run shell commands, open View -> Terminal. This will open the system shell. To see the current path, run pwd on macOS/Linux or echo %cd% on Windows

My goal is to open all the files with in a directory from the terminal. Sometimes there are many, and I want to use code .  The command always worked before, but today it didn't. When I run it code . I get -bash: code: command not found.
Based on what you said, the terminal in VS code says the interactive shell is zsh, I'm currently running bash. Is that an issue? However, in the top right corner of the terminal in VS code it says bash.
I mainly run it due to courses that I'm in. I'm still new to the coding scene. Is the terminal in VS code different than the one on my macbook?

I found my issue. It was very simple. I used the incorrect shortcut to find the search. I was using command+up+P, instead of command+shift+P.
Thank you for your help.


Better handling of ginkgo args in jenkins

@wojtek-t

@ixdy
@davidopp in lieu of quinton

Nice fix - LGTM

LGTM

@k8s-bot test this please

LGTM, thanks.

I'm not merging any code until Jenkins is green for a turn.


Integrate OpenWeather API and OpenWeather Geolocation API for Posting and Viewing Issues (Frontend)

User Story:
AS A user,
I WANT TO use the map to select a location when I post an issue,
SO THAT I can pinpoint the location of the problem and view the real-time weather for that location.
Acceptance Criteria:

The OpenWeather Geolocation API should be integrated into the issue reporting form.
Users should be able to select a location by dropping a pin on a map.
The OpenWeather API should fetch and display the weather details for the selected location (temperature, condition, etc.).
The location and weather data should be stored in the database and displayed when viewing the issue.

Tasks:

[x] : Add OpenWeather Geolocation API to Form:

Integrate OpenWeather Geolocation API in the issue reporting form
Allow users to drag and drop a pin to select a location.

[ ] Capture Location and Weather Data:

Capture the latitude and longitude from the selected location and fetch weather data using OpenWeather API.
Store both location and weather data in the database when reporting an issue.

[ ] Display Location and Weather on Issue View

Show the selected location on a map and display weather details when viewing the issue.

Completed:
Interactive Map Integration: Integrated the OpenStreetMap API using Leaflet to allow users to interact with a map. Users can select a location by clicking on the map, which records the latitude and longitude.
Location Data Capture: Successfully capturing the selected location’s latitude and longitude, which is then displayed on the Report Page and used in conjunction with the OpenWeather API to display real-time weather for that location.

In Progress:
Storing Location Data: Currently working on saving the selected location (latitude and longitude) along with the issue report in the database.

Pending:
Displaying Location on Issue View: The next step is to ensure that when users view an issue, the selected location is shown on the map.


Revert automatic wl-copy.

As stated in my original contribution[1], the wl-copy fallback was only there for people who can't make wtype work or have not installed it. Using && here will prevent the fallback from working for them because wtype command will exit with a non-zero code. Using ; instead of && would probably have made more sense.
However, always using wl-copy has the side-effect of overwriting what's in the user's clipboard, which might not be a desirable behavior if wtype works. That's why this commit reverts back to my original contribution (with && and not ;).
Maybe we could provide the ability to copy as an option (like --copy), but AFAIAC, I think it would go against the absolute simplicity of this project, so I'd argue against it.
This reverts commit 2cb7c05bb04542782120b1c4991c9532eb5974d1.
[1] https://github.com/dln/wofi-emoji/pull/10#issue-1265277835

Thank you gilbsgilbs I changed && for ;
The reason to keep
wtype "$EMOJI"; wl-copy "$EMOJI"

Is to cover the very common case of use where the user wants to repeat the same emoji many times. With whe current formula it is as easy as ctrl+v n times. I understand this decission is not gonna make everyone happy, but for now let's prioritize user experience. The script is simple enough to be modified if someone needs strict control under its clipboard for any reason.


Respect saved catalog in query context

What type of enhancement is this?
User experience
What does the enhancement do?
Greptime cloud may save catalog in query context (see #798 ), db should respect that in processing read/write. Currently only default catalog is used.
Implementation challenges
No response

Upon discussion with @sunng87 , we found that there's another issue related to the catalog used in Greptime cloud, that how to auth the full table name in SQL stmt. Full table name as in "catalog.schema.table" after the FROM token. For example, if a user only has access to his catalog "catalog_a", we need to deny executing his possible submitted SQL "select * from catalog_b.schema_a.table_a". Because SQL parsing and catalog authentication are two separate phases in current db impl, when and how to resolve the above issue remain uncertain. A possible way is through the SQL interceptor. cc @shuiyisong

Since there might be cases to use such statement(catalog.schema.table, e.g: mysql switching databases, system level metics collecting), this grammar will remain valid, and SQL level authorization will be implemented in SQL interceptor as mentioned later. cc @sunng87

Sounds good. Then we will need to check the scope of current session to see if the table operation is allowed.

Let's verify if this is already fixed.


fix(rstream-gestures): fix incorrect local position when scrolled

fixes: https://github.com/thi-ng/umbrella/issues/56
uses getBoundingClientRect() instead of offsetLeft / offsetTop

Thanks, Arthur! This went unnoticed so far, since I've only used it / needed it with fullscreen canvas in non-scrolling situations. Great, easy fix!


Adds duplicative documentation on how to receive 'withIntent' calls

👍

Coverage remained the same at 100.0% when pulling 1587c69d80df3ecc65d3be10e55f14a2286a7f50 on intent-register-documentation into 6f189b0e4ea6fabfbf770d4ae85c7dec39658757 on master.


doc: use relative instead of absolute URLs.

Links should be relative and not absolute so that they work with local godoc servers.

For instance the link from "http://golang.org/cmd/cgo/"; to
"http://golang.org/doc/articles/c_go_cgo.html"; is absolute, it should link to
"/doc/articles/c_go_cgo.html".

Can godoc create links for relative URLs or only absolute ones?

If it can create relative links it would be trivial to patch
"src/cmd/cgo/doc.go".

The same goes for the links from "http://golang.org/cmd/godoc/"; to
"http://golang.org/pkg/math/big/?m=all,text"; and
"http://golang.org/doc/articles/godoc_documenting_go_code.html";. They should
link to "/pkg/math/big/?m=all,text" and
"/doc/articles/godoc_documenting_go_code.html".

What is the expected output?
Fully working godoc without Internet connection.

What do you see instead?
Links to http://golang.org/ that could point to the local godoc server.

Which compiler are you using (5g, 6g, 8g, gccgo)?
6g

Which operating system are you using?
linux

Which version are you using?  (run 'go version')
go version devel +be6ca9f6bfe8 Fri Jan 04 17:07:21 2013 +0100 linux/amd64

Close the issue for now as it has remained inactive for more than 6 months.
Anyone with more insight into the current status may re-open the issue or add a comment about the current progress.


Add missing COMPLETE annotation to 'MultiSig' patterns.

Description

Add missing COMPLETE annotation to 'MultiSig' patterns.
Checklist

[x] Commit sequence broadly makes sense and commits have useful messages
[ ] New tests are added if needed and existing tests are updated
[ ] When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
versioning process.
[ ] The version bounds in .cabal files for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
[ ] All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages. New section is never added with the code changes. (See RELEASING.md)
[x] Code is formatted with fourmolu (use scripts/fourmolize.sh)
[x] Cabal files are formatted (use scripts/cabal-format.sh)
[x] hie.yaml has been updated (use scripts/gen-hie.sh)
[x] Self-reviewed the diff

I appreciate the attempt, but unfortunately these COMPLETE pragma are invalid, since for eras other than Shelley they do not reflect the completeness correctly. It is possible for GHC-9 to specify COMPLETE pragmas with type signatures, however until we drop support for ghc-8.10 we can't use that syntax yet.

sigh
Then know that the introduction of those new patterns creates unsolvable warnings in client code, unless we slap a wildcard pattern in a pattern-match -- which is not why we use Haskell to begin with.

Then know that the introduction of those new patterns creates unsolvable warnings in client code, unless we slap a wildcard pattern in a pattern-match

Thank you. I am very well aware of it.


When adding more than 5 sayings the latest saying should show by default

Steps:

Add more than 6 saying
Go to page 2 where you will see the 6th saying
When adding the 7th saying the page will show the first 5 sayings (page 1) instead of where the new saying is (page 2)
Also the index will show that you are on page 2 but shows the results of page 1.

@dcalvom this is still happening for me.

closed by dd2d04af7246dd594e9b6c11baedf1c0b7637761

@dcalvom this isn't fixed for me.

Fixed by https://github.com/samtecspg/articulate/commit/e7769fcbb70dceed31b5d8b4a67dcee1dbb63ac0


use share_url instead of external_url

should fix redirects on onion without breaking meta tags on share tools
test link: http://fix-series-redirect.test.theonion.com/video/onion-reviews-ghostbusters-53213

@collin @shawncook

💯 🎉

Coverage remained the same at 86.194% when pulling aa4c66236bf49a491f2cb77bcfb81df97fe813db on onion-share-tool-metatags-fix into 72fe56f07f5fa46b2712b8b71aec5c82f7efb011 on master.

Coverage remained the same at 86.194% when pulling aa4c66236bf49a491f2cb77bcfb81df97fe813db on onion-share-tool-metatags-fix into 72fe56f07f5fa46b2712b8b71aec5c82f7efb011 on master.

👍


package.json is not correct on blog entry

Hi, on your blog entry https://denisvuyka.github.io/2016/07/08/angular2-electron.html you forgot to include:
"main": "main.js",
And that makes that when executing npm start the following error appears:
[1] Error launching app
[1] Unable to find Electron app at /home/alvaro/projects/github/electron-quick-start
[1]
[1] Cannot find module '/home/alvaro/projects/github/electron-quick-start'
[1] electron . exited with code 1
Cheers.

Thanks, I will update the blog article.


References across sheets don't work

References across sheets (of the same document) don't seem to work. For example, a formula in sheet2 that says ='Sheet1':!B7 seems to be accepted, but then it gets removed and the cell is blank.

fix 1.1.3

Thank you, confirmed working in 1.1.4


CUDA out of memory. Questions about memory usage of different finetuning method on BaiChuan-7B/13B

Thanks for your fantastic work! When I use fully funetuning on BaiChuan-7B/13B, I encounter CUDA out of memory Error.
After many failed attempts, I really want to know:

How much memory I need as least to use for fully funetuning BaiChuan-7B and 13B ?
Can i use 3 gpu card to train one sequence, instead of train one sequence on each gpu? I didn't find how to do that in this git.

Many thanks and waiting your reply @hiyouga
My device:
V100 32G
Full Message:
OutOfMemoryError: CUDA out of memory. Tried to allocate 26.08 GiB (GPU 0; 31.75 GiB total capacity; 26.14 GiB already allocated; 4.77 GiB free; 26.15 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF

Full tuning of a 7B model requires 240GB VRAM, and a 13B model requires 480GB VRAM. Empirically, we should adopt DeepSpeed ZeRO-2 with 3 * A100 80GB GPUs to fine-tune a 7B model.

Full tuning of a 7B model requires 240GB VRAM, and a 13B model requires 480GB VRAM. Empirically, we should adopt DeepSpeed ZeRO-2 with 3 * A100 80GB GPUs to fine-tune a 7B model.

This is interesting because I use 8 V100 32G, which is also 240G,  but encounter CUDA out of memory Error. I use deepspeed Zero-2 following instructions and set per_device_train_batch_size=1.
Do you mean that I can train with batch-1 per machine instead of per card?
if so, how should i configure the training command?
Here is my deepspeed setting.
{   "train_micro_batch_size_per_gpu": "auto",   "zero_allow_untested_optimizer": true,   "fp16": {     "enabled": "auto",     "loss_scale": 0,     "initial_scale_power": 16,      "loss_scale_window": 1000,     "hysteresis": 2,     "min_loss_scale": 1   },     "zero_optimization": {     "stage": 2,     "allgather_partitions": true,     "allgather_bucket_size": 5e8,     "overlap_comm": false,     "reduce_scatter": true,     "reduce_bucket_size": 5e8,     "contiguous_gradients" : true   } }

Full tuning of a 7B model requires 240GB VRAM, and a 13B model requires 480GB VRAM. Empirically, we should adopt DeepSpeed ZeRO-2 with 3 * A100 80GB GPUs to fine-tune a 7B model.

This is interesting because I use 8 V100 32G, which is also 240G, but encounter CUDA out of memory Error. I use deepspeed Zero-2 following instructions and set per_device_train_batch_size=1.
Do you mean that I can train with batch-1 per machine instead of per card? if so, how should i configure the training command?
Here is my deepspeed setting. { "train_micro_batch_size_per_gpu": "auto", "zero_allow_untested_optimizer": true, "fp16": { "enabled": "auto", "loss_scale": 0, "initial_scale_power": 16, "loss_scale_window": 1000, "hysteresis": 2, "min_loss_scale": 1 }, "zero_optimization": { "stage": 2, "allgather_partitions": true, "allgather_bucket_size": 5e8, "overlap_comm": false, "reduce_scatter": true, "reduce_bucket_size": 5e8, "contiguous_gradients" : true } }
@hiyouga Really looking forward for your reply

Full tuning of Baichuan-7B with batch-size==1 on A100 80G , I also encounter CUDA out of memory Error.
Ds_config is the same as you.
I don't know how to solve it.

you can try to adopt zero-3


Support named before/after hooks in mocha

Thanks y'all! :D
See the mocha docs: https://mochajs.org/#describing-hooks
/cc @serhalp

Closing this as the current definition for mocha 3 has description: string where needed. @demands If you're still use mocha 2, you're welcome to submit a new PR with the relevant changes to the mocha_v.2.4.x definition.


Not able to view description as a separate tag in trx

When I provide multiple trx , trx-merger will give me consolidated trx, and when I convert it to html using specflow , description of the test case is missing.

I have resolved this issue but do not have rights to push those changes.


Auto detect TileMill installation

On OSX, it would be great if projectmill just detected my TileMill installation and used it by default if I don't specify otherwise using -t.
Using my packaged OSX installation works fine so far with:
./index.js render -t /Applications/TileMill.app/Contents/Resources/

Fixed with https://github.com/mapbox/projectmill/commit/81bf53ddf11ea8f9136ccfd7abfa51a80ca3de27


updated text to link for website

Hi! I updated the readme to include the link to thecodingtrain.com website.
This is my first ever github pull request :)

yay, fantastic @ziqbal! Congratulations! This is now your first merged pull request!


Deploys and where can I deploy Not working with Slack

hubot-deploy v0.13.10/hubot v2.18.0/node v5.6.0
Similar to comment from issue #86 The commands deploys and where can I deploy do not work for slack.

@kfalconer I'm working on backporting a lot of the stuff that I've been doing at work in hipchat to work in my personal slack chat. I assume you've set your tokens and hubot can identify who you are on GitHub?

So I got this mostly working in my personal slack tonight and noticed that I moved the default response for  "hubot deploys hubot" got moved to an event emission a few releases back.
If you take a look at this example you should be able to wire it up pretty easily. The "where can I deploy" behavior is here.
Now that I have everything mostly working I can hopefully figure out how to take advantage of some of the rich text formatting stuff available in slack.

Closing in favor of #86

@atmos Here is an example based on hipchat https://gist.github.com/kfalconer/f09a15661b0c4e2b74e7

@kfalconer Did you mean a slack example?

Yes, a slack example based on the existing hipchat example.

Working for you now though?

Yes, the linked example works for me.

Cool, I'll drop it in the repo as an example. Thanks.


Word Files Modified When Compiling with localdevenv.ps1

Hi Freddy,
I hope you can help me with this problem.
We used to have our own script to create our development environments (Docker containers) and now we want to use the localdenv.ps1 script. Now we have noticed the following:
When we run localdevenv, all apps in our repository are compiled correctly, etc. HOWEVER, all Word files are changed. This can be easily recognised by the fact that they are marked as changed by git. I wonder what happens here in the alc.exe that makes this happen.
Note: We use ForNAV and these Word files are accordingly also ForNAV layouts.
A first analysis of us has shown that if we open the Word files with WinRar and look at the XML files. The sorting of the elements within the DataItems has changed. At this point I doubted whether I should report it here and instead put it in the AL repository, but the files are NOT changed when I use a "AL - Package".  Toolkit           False
InstallOnlyReferencedApps       False
generateDependencyArtifact      False
CopySymbolsFromContainer        False
enableCodeCop                   False
enableAppSourceCop              False
enableUICop                     False
enablePerTenantExtensionCop     False
enableCodeAnalyzersOnTestApps   False
doNotPerformUpgrade             False
doNotPublishApps                False
uninstallRemovedApps            False
escapeFromCops                  False
doNotBuildTests                 False
doNotRunTests                   True
doNotRunBcptTests               True
useDefaultAppSourceRuleSet      False
rulesetFile
generateErrorLog                False
enableExternalRulesets          False
azureDevOps                     False
gitLab                          False
gitHubActions                   False
vsixFile
License file                    Specified
CodeSignCertPfxFile             Not specified
CodeSignCertPfxPassword         Not specified
CodeSignCertIsSelfSigned        False
KeyVaultCertPfxFile             Not specified
KeyVaultCertPfxPassword         Not specified
KeyVaultClientId
BuildOutputFile
ContainerEventLogFile
TestResultsFile                 C:\Users\MyUser\Documents\Repositories\MyProject\TestResults.xml
BcptTestResultsFile             C:\Users\MyUser\Documents\Repositories\MyProject\bcptTestResults.json
TestResultsFormat               JUnit
AdditionalCountries
PackagesFolder                  .packages
OutputFolder
BuildArtifactFolder
CreateRuntimePackages           False
AppVersion
AppBuild                        0
AppRevision                     0
SourceRepositoryUrl
SourceCommit
BuildBy                         BcContainerHelper,6.0.15
BuildUrl

the, i assume, relevant command in script ->
.\alc.exe
/project:"c:\sources\app\Shared\MyProject"
/packagecachepath:"c:\sources\app\Shared\MyProject\.alPackages"
/out:"c:\sources\app\Shared\MyProject\MyProject.app"
/assemblyprobingpaths:"C:\Program Files\Microsoft Dynamics NAV\210\Service","C:\Program Files (x86)\Open XML SDK\V2.5\lib","c:\Windows\Microsoft.NET\Assembly","C:\Test Assemblies\Mock Assemblies"

It should only update the word files if the dataset definition has changed.
If you run it a second time - is it then shuffling the word files again?

It should only update the word files if the dataset definition has changed.
In which context? The repository is freshly cloned based on the main branch. There are no changes to the AL files or Word files.
If you run it a second time - is it then shuffling the word files again?
it depends, some files changed again. Some did not. There is no pattern that I can recognize

Would it be possible for you to create a test-repository, which repros this problem either public or allow me access to this demo repo?

I was able to reproduce the issue in an test repository, unfortunately not with an simple docx file and al file but an repro still :)
I've invited you to the repository.
How to repro:

execute .\HandlerlocalDevEnv.ps1 in folder .AL-Go
Observe that after the container is created and the app (example) is compiled that the docx is changed.
Execute "AL - Package" command, observe that the file is changed once again.
start all over again at step 1

easiest way to see that there is a difference is to simply stage the change via git.

The reason for this is that there is a difference between the version of the AL Language Extension installed in your VS Code and the one running in the pipeline.
In the pipeline - the AL Language extension from the version of Business Central used to build is used:

In VS Code, you probably have

If you modify .AL-Go/Settings and add:
  "vsixFile": "latest"

Then AL-Go will always use the latest AL Language Extension for this project (you can set it in Repository settings or a global settings variable as well), then AL-Go will use the latest AL Language extension from the marketplace.
Setting it to preview will use preview, setting it to a specific URL will use a specific version.
After setting this - the .docx is no longer re-written - no changes in GIT, no new timestamp.

and.., @frottke - thanks a million for the help setting up a repro repository, which makes troubleshooting so much easier (if not possible at all).

and.., @frottke - thanks a million for the help setting up a repro repository, which makes troubleshooting so much easier (if not possible at all)

Absolutely, setting up a repro repository is the least I can do to help you troubleshooting the issue😄
The solution works perfectly. Many thanks for your commitment, even at the weekend!
I understand the reasons why the latest version is not used for the build job. But I have to admit, I don't see the reason to do the same when creating the local dev env (for active development). From your point of view, does it make sense to go for the version that is the latest, or even better, the version that is detected in Visual Studio Code? Normally, at least in my experience, developers use the latest version regardless of the project (and therefore runtime version) in Visual Studio Code.
I do have one more question about the local dev env script, but I'll create another issue for that. Should be easier for others to find an answer to that question or similar ones. This here can be closed ! 👍


Take advantage of returning assignments

Perform transformations like:
a=3;b=a*c-a
c++;d*=c
e*=f;f++

=>
b=(a=3)*c-a
d*=++c
e*=f++

This should probably wait for resolution of #272 since this functionality relies on keeping track of the order that assignments are performed in.

Duplicate of #137 .


[MINOR] Fix Typos 'an -> a'

What changes were proposed in this pull request?
an -> a
Use cmds like find . -name '*.R' | xargs -i sh -c "grep -in ' an [^aeiou]' {} && echo {}" to generate candidates, and review them one by one.
How was this patch tested?
manual tests

Test build #60003 has started for PR 13515 at commit 2531a5f.

Test build #60003 has finished for PR 13515 at commit 2531a5f.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60003/
Test FAILed.

Test build #60005 has started for PR 13515 at commit 77d3486.

Test build #60006 has started for PR 13515 at commit afa3f38.

Test build #60007 has started for PR 13515 at commit 06cb221.

Test build #60005 has finished for PR 13515 at commit 77d3486.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60005/
Test PASSed.

Merged build finished. Test PASSed.

Test build #60006 has finished for PR 13515 at commit afa3f38.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60006/
Test FAILed.

Test build #60007 has finished for PR 13515 at commit 06cb221.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60007/
Test PASSed.

Test build #60016 has started for PR 13515 at commit 6de11a6.

Test build #60016 has finished for PR 13515 at commit 6de11a6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60016/
Test PASSed.

Merged to master/2.0


Replace E2E pipelines for Kubernetes 1.17/1.18 with 1.20/1.21

As Kubernetes community releases new versions, we need to keep up and update our pipelines.
Kubernetes supports past 3 minor versions for up to 12 months (1.18 and older for up to 9 months).
Currently supported versions are 1.21, 1.20, 1.19.
https://kubernetes.io/releases/version-skew-policy/
I propose removing pipelines for versions 1.17 (and potentially 1.18), and replacing them with 1.20 and 1.21

/cc @yaron2 @msfussell @halspang @pkedy thoughts on this?

I think we should definitely have tests for whatever is officially supported. As for removing old versions, I'd be OK with that if we, again, aligned directly with kubernetes.
However, I think my ideal case would be to keep the most recent deprecated version(s) supported until we can align them with our own release/documentation cadence that gives the clear heads up we won't be testing it anymore.

I agree to adding new versions of K8s to our tests. When it comes to removing, I am concerned about us removing versions that we have a "significant" number of users still using.

I agree that we should care about user base, but Dapr is an open source project. If Kubernetes (another open source project) stops supporting certain version, so should we.
It might be different for the managed Dapr service, where we would have a dedicated team supporting paying customers.

@artursouza it would be great to be able to get that kind of information, though I don't know how we could do that across all the different k8s platforms.
Deprecation is always a careful narrative. Balancing the new features (that can not function on older k8s) and supporting older versions which stops us from making new features. Since people are free to choose what version of dapr they want to use (unlike calling into a cloud service where they fully control the stack). With that, we should be providing new features that are compelling enough to have them upgrade. I understand that this isn't always the realistic case, but it's how I see it for now at least.
If we really want to, I think it'd be reasonable to try and have some less common legacy tests run. As this is all fairly straight-forward to automate, we could have a set of old clusters that we spin up once a week (month?) and see if we've caused any major regressions during a release. This can give us some guidance and confidence on our older story without cluttering our mainline development.

There is a balance here. I tend to agree that we should only support the latest version of Kubernetes, however for widest adoption we have also been careful to make sure that Dapr can run on v1.17.x and above. To this extent we added this to the docs for v1.0 release. https://docs.dapr.io/operations/hosting/kubernetes/kubernetes-overview/#supported-versions. It would be good to be data driven here and determine how many K8s clusters are deployed for each version.

I tend to disagree :)
My concern is that once the support for a certain Kubernetes version is deprecated, the Kubernetes community stops patching fixes in that version. So, if, for example, there is a security bug, we would either have this vulnerability in Dapr, or would have to patch it ourselves (meaning that we would need to follow up on all issues and see if they apply to the deprecated versions still supported by Dapr).
For the same reason I would suggest changing the wording in https://docs.dapr.io/operations/hosting/kubernetes/kubernetes-overview/#supported-versions from 1.17.x and above to supported by Kubernetes or something like that.
The current Kubernetes version is 1.21. Officially supported versions are 1.19, 1.20, and 1.21.
Kubernetes 1.17 was released in December 2019. The last patch 1.17.17 was published in January 2021.
For comparison, the latest patch for v1.19 (1.19.12) was published a week ago.
This shows that v1.17 has already stopped getting updates. This at least should raise the issue of security, especially in this day and age.
Other service providers also follow same practices:
https://cloud.ibm.com/docs/containers?topic=containers-cs_versions
https://docs.microsoft.com/en-us/azure/aks/supported-kubernetes-versions
Another obvious but less critical argument in favor of not supporting deprecated Kubernetes versions, is that we will save significant amount of human and compute resources (considering that we are an open source project with limited resources and big plans).

What does it actually cost us to keep 1.17.x testing around? Is there any harm for us knowing that we broke something and making a decision based on that information? It is better for us as maintainers to know something doesn't work, and thus be able to exercise our judgement, and communicate to our users so that they know they need to upgrade?
I vote we keep running the tests until such time as we make an intentional decision about wether to make a change that breaks support. If there comes a future time where running the tests for 1.17.x becomes burdensome on us, we can revisit this. But it is no burden as of right now.

@wcs1only , I agree with you in general. Today it does not cost us much to test v1.17.x. But we are not testing v1.20 and v1.21.
Next month v1.22 will be available. At that point we should be testing 6 Kubernetes versions.
From my limited experience with Dapr testing pipelines, they fail on random errors relatively often. With doubled amount of the test pipelines, the chance of hitting random error will be higher, which will lead to longer development cycles. Hence the cost.
But you brought a valid point. Today we don't have a clear policy on Kubernetes version support. Perhaps it is a good chance to discuss one. IMO, it does not make sense to commit to a certain Kubernetes version (v1.17 in our case) in documentation.
Are we going to support it forever? Probably not. How often should we review/update it? It's all unclear.
And I still think that security of deprecated versions is a valid concern for users.

From my limited experience with Dapr testing pipelines, they fail on random errors relatively often. With doubled amount of the test pipelines, the chance of hitting random error will be higher, which will lead to longer development cycles. Hence the cost.

Running the tests less is not an acceptable solution to intermittent test failures. The solution to intermittent test failures is to fix them, full stop.

@dmitsh Can you send a PR adding the new K8s versions until we make a decision on deprecation?

@dmitsh Can you send a PR adding the new K8s versions until we make a decision on deprecation?

https://github.com/dapr/dapr/pull/3367

@dmitsh - You are right. Ensuring that we test and support the latest version of K8s is important and we should make this statement in the support policy for Dapr. We should also move to supporting just the current K8s support releases as per all the major cloud provider and the K8s ecosystem.  My only thoughts for keeping a test running for 1.17 were to identify any breaking changes and "minimal dependencies on K8s APIs", but given that 1.17 is deprecated this may be not as necessary.

+1 on supporting the supported Kubernetes distros.

+1 on supporting the supported Kubernetes distros.

Do you mean only supporting those or at least those?


TDC analysis fails, wrong dtype

Affecting https://github.com/SiLab-Bonn/pyBAR/blob/5a3009c72d58ace582d198b17bc628f8ab50599d/pybar/scans/analyze_source_scan_tdc_data.py#L102.
See https://github.com/scipy/scipy/issues/7273 for in-depth bug report.
I leave this open until scipy fixed the issue themselves. In the meantime, the bug can be solved by forcing the x parameter dtype to np.float64.

Yea that is pretty annoying. Had to change it in a lot of places, since I heavily use interpolation everywhere... For me it was fine to do np.float wich should automatically use the correct number of bytes according to pc architecture.

Please update scipy to 19.1.


mmod_loss consistently negative after a few steps with simple dataset

As the title says, the loss gets negative quickly and the resulting network produces random results with a ton of false positive if I let the training run and let the loss go deep in the negative.
I checked the output of
                for (auto&& x : *truth)
                {
                    if (!x.ignore)
                    {
                        point p = image_rect_to_feat_coord(input_tensor, x, sub);
                        loss -= out_data[p.y()*output_tensor.nc() + p.x()];

                        // compute gradient
                        g[p.y()*output_tensor.nc() + p.x()] = -scale;
                    }
                    else
                    {
                        // This box was ignored so shouldn't have been counted in the loss.
                        loss -= 1;
                    }
                }

Checking the loss value at line 579 of loss.h I can see the loss already gets negative at this point after a few thousands training steps, before even starting computing the truth hits, which means loss -= out_data[p.y()*output_tensor.nc() + p.x()]; is probably subtracting more than it should. What does this operation represent exactly? I don't fully understand this and it would very useful to debug.
I have attached my bounding boxes here. Nothing special, a lot of boxes close to each other (so maybe something gets double counted in the process?) but very minimal overlap.
training_resized.txt

If you post a complete program I can run that reproduces the problem I'll take a look.

It occurred to me that the problem is probably the following.  Inside the mmod_options is a overlaps_nms object that is responsible for deciding if two boxes overlap for the purposes of applying non-max suppression during detection.  When you initially create the mmod_options object it will set the overlaps_nms to the strictest notion of overlap that doesn't reject any of the boxes in your training data.  So for example, if none of your training boxes overlap then the overlaps_nms will be set to consider any boxes that overlap at all, even by a single pixel, as overlapping and will not allow any overlapping boxes in the output after non-max suppression.   Or alternatively, if the most overlap present in your training data is a 10% overlap then it won't allow any more than 10% overlap in the output.  You get the idea.
So what could happen in your case is the overlaps_nms object is configured to hardly allow any overlap, maybe 1% in your case.  However, inside the training code there are two coordinate systems.  The coordinates in the input images and the coordinates in the feature maps output by the CNN.  The code needs to map between these coordinates and back and this image->cnn->image mapping is in general not perfect since multiple image locations typically get mapped to one cnn location (since cnn feaures are often spatially downsampled at least a little relative to the input image, which is in fact the case for the example cnn architecture shown in the example program).  This means that some of your images might contain impossible labelings given the setting of the overlaps_nms object.  In your case, you have a bunch of rectangles that are right next to each other but not really overlapping.  It could easily be the case that after the image->cnn->image mapping some of them do overlap and then get thrown out during non-max-suppression.
I'm mentioning all this because the only way the MMOD loss function can go negative is essentially when the truth image labeling is impossible for the detector to output.  I have code in there that tries to validate the training data and give you an error if your boxes are "impossible" in this sense.  However, maybe the test isn't quite right and it's erroneously letting your data go by.  Although, assuming this is all true, the real problem is that the overlaps_nms is set too tight by default.
So the solution and test to see if this is happening is to change the mmod_options::overlaps_nms object to something less strict.  So set it to an overlap threshold of 0.5 for instance.  Does doing that make the problem go away?

Good idea, I noticed that reducing the size of the boxes by 25% the issue disappeared so this might work. Let me try and get back with some results.

Yeah I can confirm the error does not show up if I allow for 40% overlap

Sweet.  I'm going to make this a little less strict so hopefully others don't have the same problem.  In particular, if you instead of setting it to 0.4 replace the mmod_options::overlaps_nms setting with this:
double relax_amount = 0.95;
auto iou_thresh = options.overlaps_nms.get_iou_thresh() * relax_amount;
auto percent_covered_thresh = options.overlaps_nms.get_percent_covered_thresh() * relax_amount;
options.overlaps_nms = test_box_overlap(iou_thresh, percent_covered_thresh);

Does that work?  If so I'll make that the default setting mmod_options::overlaps_nms.

I will try this, I am just wondering, should the relax amount be <1? I am thinking it was failing with ~0 and it works alright with 0.4, so the relax amount should probably allow for an higher threshold rather than a smaller one?

Oops, right, I forgot which way it interprets it.  Yes, it definitely needs to get bigger :)
So yeah, try a relax_amount of 1.05 or 1.1 or something like that.  You will also need to make sure the _thresh parameters don't get bigger than 1 because there are asserts about that.  Wrapping them in a std::min(1.0,var) statement should do the trick.

Problem is if my boxes do not have any overlap at all  the noms iou threshold will stay at 0... should there be a baseline minimum overlap allowed?

Ah, I thought they overlapped a little.  But yeah, having a small baseline overlap is probably a good idea too.

I just pushed what we talked about to github, so this should be fixed by default now.


decodeSingle: Failed to load resource (Safari, iOS 10.1)

Hi,
On browsers that support navigator.mediaDevices.getUserMedia() I use a video input device (facingMode: environment). However on older browsers I fallback to HTML media capture.
<input type="file" accept="image/*" capture="camera">

I bind to the change event of the input.
var input = document.querySelector('input');
input.addEventListener('change',  processFile);

and when a picture is made I call:
processFile = function (e) {
    var config = {
      inputStream: { size: 800 },
      src: URL.createObjectURL(e.target.files[0]),
      ...
    }
    Quagga.decodeSingle(config, function (result) { ... });

}

This works fine for most browsers, but on mobile Safari (iOS 10.1) I get the following exception:
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (blob:https://s.codepen.io/29ce6a7c-c266-4b39-8de2-9ec61cc38455, line 0)

I debugged Quagga to see what was going on and it goes wrong in the ImageLoader.load function.
...
for (i = 0; i < htmlImagesSrcArray.length; i++) {
     img = new Image();
    htmlImagesArray.addImage(img);
    addOnloadHandler(img, htmlImagesArray);
    img.src = htmlImagesSrcArray[i];
}
...

The assignment of blob:to img.src is what causes the exception.
I reproduced this case in a small codepen.
https://codepen.io/geersch/pen/rKrwEN?editors=1010#0
Here's another demo from MDN which does the same:
https://developer.mozilla.org/en-US/docs/Web/API/File/Using_files_from_web_applications#Example_Using_object_URLs_to_display_images
Also fails for me on iOS 10.1 Safari.
Also tested with iOS 10.3.2 and there it works fine. Looking at the support matrix, I would think it should work on ios 10.1 as well:
https://caniuse.com/#feat=webworkers,canvas,typedarrays,bloburls,blobbuilder
Anybody knows what is going on?

@ericblade : Unfortunately I can't share the code. It's a private repository. Did figure out what was causing my weird issue. Turned out that the iPad device I was testing on was running iOS 10.1 beta 1. Looked over that part, noticed it when I compared it to iOS 10.1 running on a simulator.

well, i'd like to borrow the concept then, if/when I get to getting my application working in iOS :-)
So, are you saying that it works in iOS 10.1 release, but not beta? or does it not work in the release as well?

Using the live camera feed (MediaDevices.getUserMedia) works fine on iOS 11+ in Safari, but not in-app when the site is loaded via a UIWebView / WKWebView.
For lower versions of iOS you'll have to fallback to decoding the barcode via a static image. It worked fine for me on the final versions of iOS 10.3.2 (device) and iOS 10.1 (simulator). Only the iOS 10.1 beta 1 caused issues, so I'm just going to file that under "chasing a red herring".

Frankly, I didn't even know you could use a input tag to grab from a camera, seems like an early html5 thing that got quickly outdated, maybe?  But if wrapping Quagga in something that does that would allow it to work in Chrome on iOS, to some degree, then that's really kind of huge.
That said, I think I'd like to keep this open for a little bit.  I'm going to be picking up a real iOS device this weekend, probably, and if it's got 10.1, or I can put 10.1 release on it before I put it into use, I can check it out

That works fine in Chrome on iOS or any other app that utilizes WKWebView (or UIWebView).
Support is limited to mobile browsers, but that's OK as you don't really want it on desktop browsers.

Safari and Chrome Mobile for iOS 6+
Chrome Mobile for Android OS 3+
Firefox Mobile for Android OS 3+
Opera 16 for Android OS 3+

As far as I can find.
https://caniuse.com/#feat=html-media-capture


1076 autogenerated names

Pull Request Overview

Implementation of Autogenerated names controlled from Site settings
Individuals can automatically have autogenerated names for the species.
A bit more site stting refactoring to make it more scalable for odd cases such as this one.

See doc : https://docs.google.com/document/d/1tHhuixb_TY5cYhwuy4qZKrZafvFyti8qac_RRSki9NA/edit#
**Model Updates **
AutogeneratedName

guid
type
prefix
reference guid

**REST API Updates **
Site settings main block get andpost now also contain the following field
{
    'GUID': {
        'type':  'auto-species',   # mandatory
        'prefix': 'indo',          # mandatory
        'reference_guid': 'GUID',  # optional
    }
}

Yes, this PR is meant to be the first stab so the FE can start iterating.  The intention is to have a follow-up PR to update this feature based on where FE takes it.


Second draft of tutorial

Completes #361
Overview
This PR makes a second draft of the Garden tutorial based on feedback from the first draft. Some focuses were:

Keeping it as simple as possible to get the user to their first published model.
Making it harder to mess up. For example, launching a tutorial notebook with the content ready to run means there is much less copy and pasting.
Making it more self contained. All important terms are defined in context. There is no assumption that the user knows what a garden or entrypoint is.
Motivating every step. This draft assumes people want to get their models published in a way that external users can execute them, and everything ties back to that.

Discussion
Some things to note in this draft:

A lot of the content of the tutorial is now split into notebooks that the user is encouraged to open.
I made some minor code changes. That includes the new --tutorial flag to notebook start which opens the tutorial notebook. I also made it so that the local Jupyter server doesn't need a token anymore.

Testing
Just reading through the tutorial and executing the supporting materials a bunch.
Documentation
This is mostly docs.

📚 Documentation preview 📚: https://garden-ai--398.org.readthedocs.build/en/398/

The readthedocs build succeeded btw, it's just not reporting back the status for whatever reason: https://readthedocs.org/projects/garden-ai/builds/23274484/

Codecov Report
Attention: 5 lines in your changes are missing coverage. Please review.

Comparison is base (aeec103) 75.63% compared to head (eabaf5b) 75.32%.
Report is 1 commits behind head on main.

Files
Patch %
Lines

garden_ai/app/notebook.py
0.00%
5 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #398      +/-   ##
==========================================
- Coverage   75.63%   75.32%   -0.31%
==========================================
  Files          45       45
  Lines        2606     2614       +8
==========================================
- Hits         1971     1969       -2
- Misses        635      645      +10

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


Add triangle-based lines

needed as gl.lineWidth() has been removed, see https://developer.mozilla.org/en-US/docs/Web/API/WebGLRenderingContext/lineWidth

done for lines (rendering meshes with such lines is a separate issue)


Clippy (removing some panics)

Codecov Report

Merging #39 (559b49a) into main (c880dcd) will increase coverage by 0.08%.
The diff coverage is 70.68%.

@@            Coverage Diff             @@
##             main      #39      +/-   ##
==========================================
+ Coverage   84.83%   84.92%   +0.08%
==========================================
  Files          46       46
  Lines        6878     6857      -21
==========================================
- Hits         5835     5823      -12
+ Misses       1043     1034       -9

Impacted Files
Coverage Δ

src/lib.rs
1.24% <3.12%> (-0.02%)
:arrow_down:

src/utils.rs
47.01% <75.00%> (ø)

src/sqrt.rs
89.79% <87.50%> (+11.15%)
:arrow_up:

src/compress.rs
98.06% <100.00%> (+0.48%)
:arrow_up:

src/srs.rs
93.05% <100.00%> (-0.31%)
:arrow_down:

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


Documenting RPC calls

OpenBazaar has 8 RCP messages. I'm trying to wrap my head around them.

PING, STORE, FIND_NODE, FIND_VALUE are described in the Kademlia paper
STUN, HOLE_PUNCH seem to be NAT related
DELETE seems to be to delete key-value pairs from the DHT
What are INV, VALUES?

Where are RPC calls documented?

There aren't documented anywhere.
The INV/VALUES works like INV/GETDATA in bitcoin. Instead of bombarding a node with store requests for data it might already have, it sends an INV packet with hashes and the node requests only those hashes it needs. Which are sent in the VALUES packet.


Suggestion for .tabs class

I suggest you to add 2 lines:
max-width: 100%;
overflow-x: hidden;
After the last update, i got scrollable tabs everywhere.

+1
same issue on chrome (ver: 45.0.2454.85), however firefox (ver: 38.4.0) doesn't have the problem
see: https://jsfiddle.net/9ma5muf4/2/
however suggested solution works OK for both.

Closing in favor for https://github.com/Dogfalo/materialize/issues/4400


Window failed to install sharp.

error E:\Gatsby\my-blazing-fast-site\node_modules\sharp: Command failed.
Exit code: 1
Command: (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
Arguments:
Directory: E:\Gatsby\my-blazing-fast-site\node_modules\sharp
Output:
info sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.8.1/libvips-8.8.1-win32-x64.tar.gz
ERR! sharp connect ETIMEDOUT <IP_ADDRESS>:443
info sharp Attempting to build from source via node-gyp but this may fail due to the above error
info sharp Please see https://sharp.pixelplumbing.com/page/install for required dependencies
E:\Gatsby\my-blazing-fast-site\node_modules\sharp>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "" rebuild )
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| win32 | x64
gyp info find Python using Python version 3.6.6 found at "C:\Program Files\Python36\python.exe"
gyp http GET https://nodejs.org/download/release/v12.13.0/node-v12.13.0-headers.tar.gz
gyp http 200 https://nodejs.org/download/release/v12.13.0/node-v12.13.0-headers.tar.gz
gyp http GET https://nodejs.org/download/release/v12.13.0/SHASUMS256.txt
gyp http GET https://nodejs.org/download/release/v12.13.0/win-x86/node.lib
gyp http GET https://nodejs.org/download/release/v12.13.0/win-arm64/node.lib
gyp http GET https://nodejs.org/download/release/v12.13.0/win-x64/node.lib
gyp http 200 https://nodejs.org/download/release/v12.13.0/SHASUMS256.txt
gyp http 200 https://nodejs.org/download/release/v12.13.0/win-x86/node.lib
gyp http 200 https://nodejs.org/download/release/v12.13.0/win-x64/node.lib
gyp http 404 https://nodejs.org/download/release/v12.13.0/win-arm64/node.lib
gyp ERR! find VS
gyp ERR! find VS msvs_version not set from command line or npm config
gyp ERR! find VS VCINSTALLDIR not set, not running in VS Command Prompt
gyp ERR! find VS could not use PowerShell to find Visual Studio 2017 or newer
gyp ERR! find VS looking for Visual Studio 2015
gyp ERR! find VS - not found
gyp ERR! find VS not looking for VS2013 as it is only supported up to Node.js 8
gyp ERR! find VS
gyp ERR! find VS **************************************************************
gyp ERR! find VS You need to install the latest version of Visual Studio
gyp ERR! find VS including the "Desktop development with C++" workload.
gyp ERR! find VS For more information consult the documentation at:
gyp ERR! find VS https://github.com/nodejs/node-gyp#on-windows
gyp ERR! find VS **************************************************************
gyp ERR! find VS
gyp ERR! configure error
gyp ERR! stack Error: Could not find any Visual Studio installation to use
gyp ERR! stack     at VisualStudioFinder.fail (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:121:47)
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:74:16
gyp ERR! stack     at VisualStudioFinder.findVisualStudio2013 (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:351:14)
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:70:14
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:372:16
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\util.js:54:7
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\util.js:33:16
gyp ERR! stack     at ChildProcess.exithandler (child_process.js:302:5)
gyp ERR! stack     at ChildProcess.emit (events.js:210:5)
gyp ERR! stack     at maybeClose (internal/child_process.js:1021:16)
gyp ERR! System Windows_NT 10.0.17763
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd E:\Gatsby\my-blazing-fast-site\node_modules\sharp

The salient part of this error is:
info sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.8.1/libvips-8.8.1-win32-x64.tar.gz
ERR! sharp connect ETIMEDOUT <IP_ADDRESS>:443
info sharp Attempting to build from source via node-gyp but this may fail due to the above error

This means there was a (temporary) networking problem between the machine this was run on and <IP_ADDRESS>.

I hope this information helped. Please feel free to re-open with more details if further assistance is required.

You shoudl add a support of offline installation of all dependencies such as libvips and node headers. It's really a pain to install anything in a very restricted corporate environment.


Argument type: duration

The most of Discord bots are expected to provide "mute" and "ban" commands. Their implementation involves juggling with parsing strings just to get so-much-desired duration.
Formats:

"3w 1d 11 [many spaces]h \t30m 20s 5ms"

Methods:

duration.toWeeks() -> float
duration.toDays() -> float
duration.toMinutes() -> float
duration.toSeconds() -> float
duration.toMilliseconds() -> float

And perhaps a few aliases:

duration.toW()
duration.toD()
duration.toM()
duration.toMs()

etc

This would make my bot so much cleaner haha!

Would Commando handle parsing a duration itself or use an external package like moment.js or date-fns to handle it?

It should parse the duration itself. Cutting down dependencies is usually
welcome.
On Mon, Dec 10, 2018, 11:42 PM Jonah Snider<EMAIL_ADDRESS>wrote:

Would Commando handle parsing a duration itself or use an external package
like moment.js or date-fns to handle it?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/discordjs/Commando/issues/182#issuecomment-446070397,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AiKPagU7_swl7tQjMAPp56NdB8yU_Pxzks5u3ze_gaJpZM4V4Ls9
.

I'm not opposed to using moment, since it covers a lot of possible input formats, and handles localisation. The only problem is it doesn't take the "6mo3d4h50m30s" format... which is something that, ideally, would also accept locale-specific suffixes.

Hi, I am working on a solution to this but I am having difficulty testing it locally.  I'm currently attempting to run the test bot included but receiving this error:
 $ node test/bot.js
/Users/madlab/repos/temp/Commando/src/extensions/message.js:7
module.exports = Structures.extend('Message', Message => {
                            ^

TypeError: Cannot read property 'extend' of undefined
    at Object.<anonymous> (/Users/madlab/repos/temp/Commando/src/extensions/message.js:7:29)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3)
    at Module.require (module.js:596:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/Users/madlab/repos/temp/Commando/src/registry.js:5:25)
    at Module._compile (module.js:652:30)

This is after a npm install and npm install discord.js. I ran into the same errors with npm link to my own bot locally.

Okay I have this mostly done but I can't seem to get the methods working. Just adding them to my DurationArgumentType class doesn't seem to do the trick. I also didn't find any examples of with the rest of the types.

This is the regex I'm using to parse duration in one of my bots, not sure if it's any help to anybody:
^(?:(?<weeks>\d+)w)?(?:((?<days>\d+)d)?(?:(?<hours>\d+)h)?(?:(?<minutes>\d+)m)?)$
E.g. 2w3d4h15m where any part is optional

I'm not opposed to using moment, since it covers a lot of possible input formats, and handles localisation. The only problem is it doesn't take the "6mo3d4h50m30s" format... which is something that, ideally, would also accept locale-specific suffixes.

Moment supports plugins which you can use to define new formats and date-fns lets you define a pattern for parsing dates.

I'm guessing this was dropped, by people who tried to make it work?
If so, I would like to give it a shot, and see what I can come up with.

I've given this a shot using code from my own bot (#366). I think this would make a great addition to Commando and would love to see any of the suggested implementations merged!

I've given this a shot using code from my own bot (#366). I think this would make a great addition to Commando and would love to see any of the suggested implementations merged!

I have the same errorhttps://prnt.sc/1tkskl4


Infinite Initializing application on Mobile

Hi everyone,
I started using Phonegap some days ago. Trying to use https://build.phonegap.com to build an apk for Android.
It worked, i downloaded this apk thanks to the QR Code, installed it on my Huawei Honor 8, with Android 6.0 version.
When I launch the application, "Hydra" ask me to update my application, it retrieve new contents.
And then, i have a "Initalizing. Please wait" page, but, nothing happen. I waited for 30 min to see if something changed, but, the loading icon does not stop to turn.
I attach with this my config.xml, if you need something else, don't hesitate to ask me :)
Best regards, D.Braz.
confing.txt

https://github.com/phonegap/phonegap-start/issues/210


Feature: Add Image Size Threshold for Cleanup

Description: Introduce an option to delete Docker images larger than a specified size. Users can pass a flag like --larger-than 500MB to remove images above the given size limit.
Example:

./dockclean --larger-than 500MB

Hi @mmuazam98, could you also assign this one to me.

Hi @mmuazam98, I've completed this issue #12 too, could you please review and merge this ASAP.
I'll update you soon on the issue #6
Thanks!


Adding CSS files

I am going to add a new CSS file in a CSS folder which i will be creating.

Go ahead! @Kakroo

@Kakroo Finally we've got CSS folder in our repository for others to contribute to. All thanks to your contribution. Hope to see more from you in the future. Have a great New Year

@Kakroo Finally we've got CSS folder in our repository for others to contribute to. All thanks to your contribution. Hope to see more from you in the future. Have a great New Year


Read graph from rdflib rather than from (io) file?

Is there a way to read/assign an ontology/graph directly from rdflib to ontospy, rather than from a file/url or g.serialize()?
I'm generating ontologies via automation and would like to render their tree/documentation for client side ui and would rather not serialize/persist and then have to parse into ontospy.
Please advise?
Thanks a bunch!

Hi @lambdamusic,
I am new contributor to this project and based on my understanding of the codebase, I have raised a PR for resolving this issue. Kindly review it :smile:


Revert "rafthttp: fix wrong return in pipeline.handle"

Reverts coreos/etcd#3737

Thanks.

Sorry for the mistake.


[Ignore this PR] Testing Pipeline with self-hosted runner

[ ] This contribution adheres to CONTRIBUTING.md.

TODO: Check the above box with an 'x' indicating you've read and followed CONTRIBUTING.md.
What does this Pull Request accomplish?
TODO: Include high-level description of the changes in this pull request.
Why should this Pull Request be merged?
TODO: Justify why this contribution should be part of the project.
What testing has been done?
TODO: Detail what testing has been done to ensure this submission meets requirements.

Closing this PR and addressing the comments in https://github.com/ni/measurementlink-python/pull/479


fix: radix config add export

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Robotoff questions disappear if you slide tabs until the Analysis tab

Robotoff questions disappear if you slide tabs until the Environment tab.
They appear again when reopening the product again
https://user-images.githubusercontent.com/1689815/119821066-6cb38700-bef2-11eb-8710-9769504b78f3.mp4

Can still reproduct in latest commit/build

Still here


Availability: Enable "Sections" to be keyboard-friendly

When "tabbing" through all buttons on the page, the "sections"-option is skipped.

this is fixed in this commit, by splitting up the "sections button".


12 npm audit

This shouldn't be reviewed/merged until at least after node and other packages are updated--the updates will probably solve some of the CI / audit failures.

Migrated to yarn instead of npm, so no longer required. Yarn audit ticket here: https://github.com/button-inc/digital_marketplace/issues/132


Webpack plugin to detect case mismatch in requires

Addresses #240.
Plugin works as advertised, both with requires and imports.
I was not sure if we need this in prod, so only included in dev for now. Also, pinned the version as with other dependencies.

Can you assess the performance impact of this on recompiles?
You can import a large project into a create-react-app app, and see how much time it takes to save a file before and after this change.
We want to make sure it doesn’t slow down the rebuilds.

By importing do you mean creating a new app via create-react-app, and then just copying sources over?

Doesn’t really matter, I just want to check what happens when there are many modules.

(To be clear, what you suggested sounds like a good way, yes.)

I have a mid-size project handy (~10k lines), taking ~15s on the initial startup, recompiles take a fraction of a second with or without the plugin. I wonder if recompiles on a bigger project (like React at 50k lines) would be seriously slower, but it's hard to make a complex project compile without bringing in all the infrastructure.

Looking good, thank you.


Message Analyzer is dead

[Enter feedback here]
Since Message Analyzer is dead, how are we supposed to analyse these things?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 69242460-9916-0cca-0858-a36f7f427991
Version Independent ID: c154f1d7-ec73-2d8d-5fd8-7adf18b668a5
Content: Troubleshooting a Failover Cluster using Windows Error Reporting
Content Source: WindowsServerDocs/failover-clustering/troubleshooting-using-WER-reports.md
Product: windows-server
Technology: storage-failover-clustering
GitHub Login: @dcuomo
Microsoft Alias: vpetter

I am not sure if you will get any answers here to your question, at least not anytime soon.
You may want to look elsewhere for answers, unless you have suggestions for improving one or more specific pages in the MS Docs repository.
Disclaimer: I am not affiliated with Microsoft or the Microsoft Docs teams here on GitHub.
The intention of this repository is to improve on the existing documentation by providing the users a way to report factual errors, improvement suggestions and request updates for new versions.
The MS Docs team members might not have time to answer your question, both due to the small size of the team and the big workload.
Try the following resources to get in touch with users who may be able to help you:

TechNet forums: https://social.technet.microsoft.com/Forums/en-US/home
MSDN: https://social.msdn.microsoft.com/Forums/en-US/home
Microsoft Community: https://answers.microsoft.com/

I don't want to shoot the messenger, but....  you are basically saying Microsft does not care about the customers and the customer base should try to find everything out themselves? I expected something like this, but I still have some hope.
Btw: I expect a product that is being sold having a good documentation. I am very disappointed by what Microsoft is delivering here not only in this specific topic but on docs.microsoft.com.

Sorry if my message gives the impression that Microsoft does not care.
I am merely trying to ask if this is meant to be a report that the document page needs to be changed, and if yes, then how do you recommend that it should be changed.
My other advices in my previous comment was meant to provide you with alternatives, in case you want to troubleshoot an issue on your side, especially if the issue is not proven to be happening with everybody else all over the world (or at least all those who use the exact same software configuration as you).

Also, if you are trying to troubleshoot a problem on your own computer, you may want to contact your nearest Microsoft Support department, to make sure that any undocumented issues are coexisting with the issue you are reporting here.

Yes, of course my report is here because the page needs to be changed! really, why else would I invest my time to put it up?
The tool "message analyzer" that is referred to on the page is simply not available anymore. Microsoft just deleted it. While it is ok for them to do that - it's their software - we need a different approach now. So you either update the page with info on how to do it with tools that are actually available or you just delete the page and let that information die with it

Sorry for appearing to be slow and hard of understanding, there are quite a lot of users who open tickets here to ask for support to resolve issues local to their own computers.
Thank you for your feedback. Let us hope that the MS Docs team will soon let us know of any plans to change the page.

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


Add detail on networks

We could talk more about networks.  e.g.

each container gets it's own IP address
demonstrate DNS resolution on explicitly-created networks
network drivers?

Did the first two.
Network drivers is probably a bit advanced for "intro".


backend, model: remove calls to trivial super().init() methods

These are unsafe, according to mypy:
error: Call to abstract method "__init__" of "DataSpecificationContent" with trivial body via super() is unsafe  [safe-super]

LGTM


updating readme and scripts to upload

@sumitarora since do not need to modify the application level code anymore in order to get Batarangle to work (as ng.probe is available in angular 2 dev mode) we should remove this from limitations then (or wherever else we are mentioning it), but mention somewhere that angular 2 needs to run in dev mode (it's default mode, please confirm) in order for batarangle to work.

@igor-ka done

@sumitarora LGTM :shipit:


Feature/5 word page

Implemented the word page with some changes mentioned in the previous PR.
Changes:
Links
All of the links in the app are now using  tag with href property (combination of Link components from Material UI and react-router-dom). That allowed us to get rid off the unnecessary callback functions on clicks. This issue was mentioned in the previous PR.
TermAPI
Implemented fetching of the terms.
DefinitionSnippet
Added a new component showing the definition of the term. There are some things I want to discuss, please refer to the questions section of this text.
DisambiguationPage
Dropped the useEffect hook. The original intent was to have bullet proof mechanism if the user starts messing with the URL, but for now it was doing more harm than good, so I got rid off it.
TermResult
Added a new component resposible for showing the Term results. I think it is better to have a separate TermResult than to have one big component SearchResult. Search result is still used for words and terms on the search page but on the disambiguation page it just didn't look right.
SearchBar
The decision where the user is redirected is moved here. Originally it was in the SearchPage component, but as mentioned in the previous PR it wasn't the best solution.
Utils
Added some static functions which help with creating API requests.
NoResult
Added basic no result component.
Other notes:
In some parts of the app the responsivness is not ideal (as mentioned in the previous PR). I created a new issue which addresses this issue. I will take care of it in the near future. So for example the NoResults component is written in a way that was the quickest. I will rewrite it while solving the responsivness issue.
Questions:

How do we want to shorten the definition of the term presented on the word page? Currently it just shows some number of characters. What if we showed only first three lines ? Don't know how hard it will be considering responsivity but if it would be desired I am willing to do it.
How to sort the results on the word page? The sorting is now non-existing. Do we want to show the terms with definitions first and then everything else?

Solves #6

How do we want to shorten the definition of the term presented on the word page? Currently it just shows some number of characters. What if we showed only first three lines ? Don't know how hard it will be considering responsivity but if it would be desired I am willing to do it.

Couple of lines would be perfect, I left a comment in the code how to achieve that.

How to sort the results on the word page? The sorting is now non-existing. Do we want to show the terms with definitions first and then everything else?

It does not matter at this point, as long as the sort is stable (i.e. does not change on page reload). This should be IMHO handled by the API.


Can this connector be used to pull the data given by ACM Exports directly in to PowerBI

Can this connector be used to pull the data given by ACM Exports directly in to PowerBI  ? In detail, I do not intend to use Exports or APIs and storage account.  I want to pull that Exports data directly into PowerBI may be at subscription level or management group level.
Is that something supported with this connector ?

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

ID: 97d9cf44-77fd-5d70-0d6f-d7cefc1458c6
Version Independent ID: 62c502c1-1831-c94e-d804-f71cb6a569a3
Content: Connect to Azure Cost Management data in Power BI Desktop - Power BI
Content Source: powerbi-docs/desktop-connect-azure-cost-management.md
Service: powerbi
Sub-service: powerbi-desktop
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Thanks for your comment, @hisathya.
This looks like a support request or product question rather than documentation feedback.
You might find a solution in the Power BI Community. If not, try our support page.


Release 24.02.0

The week before the release

[ ] Ensure CI is green
[ ] Create release branch from main to freeze commits, like so:

RELEASE=24.02.0
git fetch origin
git checkout origin/HEAD
git switch --create release/$RELEASE
git push origin release/$RELEASE

[ ] If any changes are made in the harvest autosupport repository, please update the harvest-metrics repository main branch with the latest asup_linux_amd64 binary. This binary can be generated using Jenkins with the following parameters:

Field
Value

VERSION
24.02.0

RELEASE
1

BRANCH
release/24.02.0

ASUP_MAKE_TARGET
production

DOCKER_PUBLISH
false

RUN_TEST
true

OVERWRITE_DOCKER_LATEST_TAG
false

[ ] Create a release branch for the harvest-metrics repo like so:

RELEASE=24.02.0
git clone https://github.com/NetApp/harvest-metrics.git
cd harvest-metrics
git checkout origin/HEAD
git switch --create release/$RELEASE
git push origin release/$RELEASE

[ ] Ensure all issues for the release are tagged with status/testme and unassigned. Use gh or the GitHub UI to do this.
[ ] Use the release issue burn down list to verify issues are fixed. Move status/testme issues to status/open or status/done
[ ] Ensure that the release is validated against NABox.
[ ] Ensure that the release is validated against FSX.
[ ] Use Jenkins to create release artifacts for test machines
[ ] Create changelog

[ ] Draft a new release. Use v$RELEASE for the tag and pick the release/$RELEASE branch. Click the Generate release notes button and double check, at the bottom of the release notes, that the commits are across the correct range. For example: https://github.com/NetApp/harvest/compare/v23.11.0...v24.02.0
[ ] Copy/paste the generated release notes and save them in a file pbpaste > ghrn_$RELEASE.md
[ ] Generate draft release highlights by executing go run pkg/changelog/main.go new. This will create a file named releaseHighlights_$RELEASE.md. Edit that file to add content (example content)

[ ] Ensure all notable features are highlighted
[ ] Ensure any breaking changes are highlighted
[ ] Ensure any deprecations are highlighted

[ ] Generate changelog by running

go run pkg/changelog/main.go --title $RELEASE --highlights releaseHighlights_$RELEASE.md -r ghrn_$RELEASE.md | pbcopy

[ ] Open a PR against the release branch with the generated release notes for review
[ ] PR approval

Update Metrics Documentation
bin/harvest generate metrics --poller POLLERNAME

[ ] Make sure docs look good and open a PR for review with docs/ontap-metrics.md changes

The day of the release

[ ] Create a new build from Jenkins (details)

[ ] Click Build with Parameters and fill in the appropriate fields. Here's an example, where RELEASE=24.02.0

Field
Value

VERSION
24.02.0

RELEASE
1

BRANCH
release/24.02.0

ASUP_MAKE_TARGET
production

DOCKER_PUBLISH
true

RUN_TEST
true

OVERWRITE_DOCKER_LATEST_TAG
true

[ ] Draft a new release. Use v$RELEASE for the tag and pick the release/$RELEASE branch.
[ ] Type $RELEASE in the Release title text input
[ ] Open the CHANGELOG.md file, copy the single $RELEASE section at the top, and paste into the release notes text area.
[ ] Ensure the Set as the latest release checkbox is selected
[ ] Ensure the Create a discussion for this release  checkbox is selected
[ ] Upload the artifacts from the Jenkins build above and attach to the release
[ ] Click Publish release button
[ ] Announce on Discord
[ ] Publish latest docs to netapp.github.io

[ ] Make sure you're on the release branch git switch release/$RELEASE
[ ] The documentation version selector uses the short form of the release, so 24.02 NOT 24.02.0

mike deploy --push --update-aliases $SHORT latest

[ ] Merge release branch into main. The PR should use the chore:  prefix

@Hardikl will run release process for 24.02


#16340 allow null for calendar

Closes #16340

Let's use zero time (1970?) instead of current time for nulls

Still the same

Hint about current time doesn't appear when switching from text value

Verified


There doesn't appear to be a way to get the minimum disk required for a given ImageReference

If you try and provision a new virtual machine with a virtual hard disk size less than what is required by a VHD image, an error is reported in the console saying that disks cannot be resized downwards, but there does not appear to be away to know what the minimum disk size should be.

Unfortunately, compute service does not provide us size via  VirtualMachineImage.osDiskImage property.
Also after creating the virtual machine from such image, service won't include this information in the VM payload as well. Only option i am aware of is to check the size of OS vhd using storage data API.

as per above, this is not actionable currently in the SDK beyond the suggested workaround.


Remove guava from dependencies

Looks like it is not used nor in the publisher neither transitively by other dependencies.

Thank you @Aloren for spotting this obsolete dependency - that must have been there unused since the very beginning ... I comment one small thing on dependencies ordering.

@cstettler Thanks for the review! Done.

Fixes #164


Upgrade aws-apigateway-importer

Now sitting at https://github.com/awslabs/aws-apigateway-importer/commit/fea51c9d2a604f40a10ee26d51bca092bc274775
Upgrade was specifically to address https://github.com/awslabs/aws-apigateway-importer/issues/192

As it's a direct merge from upstream, I'm not going to peer into it too closely. It seems to work for me.


Replaced deprecated method call pointer nbUInt8AtOffset  with call to…

… uint8AtOffset: .

It would be nice to see this merged. @guillep ?


BUG

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots or other media to bug

@jus1d closed


docs: IFPS --> IPFS

Some typo fixes 😄

Thanks! Would  you mind adding the DCO signoff here: https://github.com/textileio/docs/pull/139/checks?check_run_id=678389683

Sorry, done!

Thanks!


Authentication subsection renamed to Security

Also moving basic access control to security.

Jenkins job istio.github.io/presubmit passed

Jenkins job istio.github.io/presubmit passed


PatternFly updates post migration

General UI improvements around task list and details as well as process list and details.

@cristianonicolai this is looking nice!

+1

merged in master

@Salaboy thanks, I'll try to review other parts of our workbench as time allows.


Unpublished item should not be deleted, it shall only be marked as unpublished in Recombee

Description
Currently, the DeleteItem endpoint of the Recombee API is being called in a webhook in case a post is unpublished:

https://github.com/Kentico/kontent-example-integration-recombee/blob/44bf033ca3e64aadc56737703e1fe12b54f5719e/src/lambda/model/recombee-client.ts#L104
https://github.com/Kentico/kontent-example-integration-recombee/blob/c35289ff1324337cb226ed49963abefc931cd850/src/lambda/recombee-sync-webhook.ts#L93
.

However, the post shall be only marked as unpublished using an item property, as deleting the item also removes all the associated interactions from Recombee.
See https://docs.recombee.com/reql_filtering_and_boosting.html#handling-deleted-items.

I'll take a look, thanks!

@OndraFiedler we discussed this internally, and although we understand what's happening, we don't want to enforce a set model property onto the user, that he needs to filter by (e.g. if we decide that everybody has to have a "published" property in their model and they will ALWAYS need to filter by that property to recommend valid content). This is just a sample integration, so the customer is always free to update it as they see fit, but I would almost see this as a feature to be added directly into recombee. It could have a special method for a "soft" delete that will just hide the data instead of removing them so the models are not being affected and the user experience is not affected.