Pinning affects an external OpenMP library

TLDR: An external OpenMP-equipped C++ library shows no parallel speedup when thread pinning is used. Disabling pinning fixed the issue.
https://discourse.julialang.org/t/openmp-in-a-shared-library-opened-in-julia/113880/9

Are you perhaps oversubscribing CPU cores? That is, are Julia threads and the external OpenMP threads maybe running on the same set of CPU cores? This would explain why it works better without thread pinning, because the OS scheduler then has the flexibility to avoid this (as much as possible).
If that's the case you should either avoid thread pinning (as you did) or pin the OpenMP threads as well (e.g. through environment variables) - to different cores, of course.
Otherwise, pinthreads shouldn't effect any OpenMP threads: Julia threads aren't even OpenMP threads, they are pthreads.

I do not think the cpu cores are oversubscribed. When the library is called, only a single thread is running.

I don't understand, I thought you have multiple threads? Why would pinning or not pinning make a big/any difference if there is only a single thread?
In any case, pinthreads doesn't change anything about other OpenMP threads. Hence, AFAICS, this isn't a bug in ThreadPinning.jl.
(Also, you neither provide much information nor a MWE, which makes this hard/impossible to figure out.)

The issue was intended as a heads up. I'm working on a minimal working example.
The application runs with multiple threads. However at the point where the library gets called, only a single thread is running.

The issue is real: enabling or disabling pin threading affects the performance of the external library.

To be clear, I'm not arguing that your performance issue isn't real. I'm saying that it (almost certainly) isn't a bug in ThreadPinning.jl.
Of course, feel free to continue the discussion in the Discourse thread. However, much more information will be needed, like:

When you call into the library from - IIUC - a single Julia thread, how many OpenMP threads are active?
Where are the OpenMP threads running? Have you pinned them? If so, how?
Which system are you running on? Laptop? Cluster? Which CPU?
Is data passed between Julia and the library? If so, is the data, perhaps, local to the Julia thread but far away from the OpenMP thread(s)?
...

Here is the minimal working example (https://hogwarts.ucsd.edu/~pkrysl/shared/mwe_eclgraphcolor.tgz).
Here is a sample output:

pkrysl@horntail:~/mwe_eclgraphcolor$ . ./run_mwe.sh
================================================================================
With 1 thread
================================================================================
  Activating project at `~/mwe_eclgraphcolor`
[ Info: Loading ThreadPinning
   Resolving package versions...
  No Changes to `~/mwe_eclgraphcolor/Project.toml`
  No Changes to `~/mwe_eclgraphcolor/Manifest.toml`
    Updating git-repo `https://github.com/PetrKryslUCSD/ECLGraphColor.jl.git`
   Resolving package versions...
  No Changes to `~/mwe_eclgraphcolor/Project.toml`
  No Changes to `~/mwe_eclgraphcolor/Manifest.toml`
    Building ECLGraphColor → `~/.julia/scratchspaces/44cfe95a-1eb2-52ea-b672-e2afdf69b78f/28351fdf0c4c6de0974f0f560c914d6bfd9411dc/build.log`
  0.560385 seconds
  Activating project at `~/mwe_eclgraphcolor`
[ Info: NO ThreadPinning
    Updating git-repo `https://github.com/PetrKryslUCSD/ECLGraphColor.jl.git`
   Resolving package versions...
  No Changes to `~/mwe_eclgraphcolor/Project.toml`
  No Changes to `~/mwe_eclgraphcolor/Manifest.toml`
    Building ECLGraphColor → `~/.julia/scratchspaces/44cfe95a-1eb2-52ea-b672-e2afdf69b78f/28351fdf0c4c6de0974f0f560c914d6bfd9411dc/build.log`
  0.498791 seconds
================================================================================
With 2 threads
================================================================================
  Activating project at `~/mwe_eclgraphcolor`
[ Info: Loading ThreadPinning
   Resolving package versions...
  No Changes to `~/mwe_eclgraphcolor/Project.toml`
  No Changes to `~/mwe_eclgraphcolor/Manifest.toml`
    Updating git-repo `https://github.com/PetrKryslUCSD/ECLGraphColor.jl.git`
   Resolving package versions...
  No Changes to `~/mwe_eclgraphcolor/Project.toml`
  No Changes to `~/mwe_eclgraphcolor/Manifest.toml`
    Building ECLGraphColor → `~/.julia/scratchspaces/44cfe95a-1eb2-52ea-b672-e2afdf69b78f/28351fdf0c4c6de0974f0f560c914d6bfd9411dc/build.log`
  0.564154 seconds
  Activating project at `~/mwe_eclgraphcolor`
[ Info: NO ThreadPinning
    Updating git-repo `https://github.com/PetrKryslUCSD/ECLGraphColor.jl.git`
   Resolving package versions...
  No Changes to `~/mwe_eclgraphcolor/Project.toml`
  No Changes to `~/mwe_eclgraphcolor/Manifest.toml`
    Building ECLGraphColor → `~/.julia/scratchspaces/44cfe95a-1eb2-52ea-b672-e2afdf69b78f/28351fdf0c4c6de0974f0f560c914d6bfd9411dc/build.log`
  0.280195 seconds
================================================================================
With 4 threads
================================================================================
  Activating project at `~/mwe_eclgraphcolor`
[ Info: Loading ThreadPinning
   Resolving package versions...
  No Changes to `~/mwe_eclgraphcolor/Project.toml`
  No Changes to `~/mwe_eclgraphcolor/Manifest.toml`
    Updating git-repo `https://github.com/PetrKryslUCSD/ECLGraphColor.jl.git`
   Resolving package versions...
  No Changes to `~/mwe_eclgraphcolor/Project.toml`
  No Changes to `~/mwe_eclgraphcolor/Manifest.toml`
    Building ECLGraphColor → `~/.julia/scratchspaces/44cfe95a-1eb2-52ea-b672-e2afdf69b78f/28351fdf0c4c6de0974f0f560c914d6bfd9411dc/build.log`
  0.595618 seconds
  Activating project at `~/mwe_eclgraphcolor`
[ Info: NO ThreadPinning
    Updating git-repo `https://github.com/PetrKryslUCSD/ECLGraphColor.jl.git`
   Resolving package versions...
  No Changes to `~/mwe_eclgraphcolor/Project.toml`
  No Changes to `~/mwe_eclgraphcolor/Manifest.toml`
    Building ECLGraphColor → `~/.julia/scratchspaces/44cfe95a-1eb2-52ea-b672-e2afdf69b78f/28351fdf0c4c6de0974f0f560c914d6bfd9411dc/build.log`
  0.155279 seconds
pkrysl@horntail:~/mwe_eclgraphcolor$

Two Julia files are provided: one adds, uses ThreadPinning (mwe_w.jl). This one does not get any speed up on the graph calculation.
The other one does (mwe_wo.jl).

@carstenbauer Carsten, I am not saying that it is a bug in ThreadPinning. It would be interesting to find out why thread pinning affects OpenMP threads, though. Wouldn't you agree?


News Category Filter enhancement for Mobile View

The Category Filter gets moved to the bottom of the News Page for mobile view.  Consider moving this to the top, discuss with Nate on options.
Current Site

Nate agreed it should be placed at the top.


[Bug]Jobs discovering and attempting parse potentially premature manifest - v12

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
Current Version: DBT 1.7
In DBT Cloud and DBT Cloud CLI, a job is discovering and attempting to parse a manifest version (V12) that is not yet listed publicly on any DBT documentation. According to DBT documentation, V12 is not a valid manifest version. Upon examining manifest V12, it appears it is for an unreleased version of DBT.
No changes were made to our DBT versioning and
Link to V12 manifest schema: https://schemas.getdbt.com/dbt/manifest/v12.json
{
  "properties": {
    "metadata": {
      "type": "object",
      "title": "ManifestMetadata",
      "description": "Metadata about the manifest",
      "properties": {
        "dbt_schema_version": {
          "type": "string"
        },
        "dbt_version": {
          "type": "string",
          "default": "1.9.0a1"
        }
      }
    }
    ...
  }
}

Expected Behavior

DBT Cloud and DBT Cloud CLI should only discover and parse manifest versions that are publicly documented and valid according to the current DBT documentation.
When using DBT 1.7, the job should not encounter or attempt to parse manifest version V12, as it is not listed in the public documentation and appears to be for an unreleased version of DBT.
The job should correctly identify and parse the appropriate manifest version (up to V11) as specified in the current DBT documentation.

Steps To Reproduce
dbt deps
dbt build --select state:modified+1
Relevant log output
# DBT Job commands:
dbt deps
dbt build --select state:modified+1

# Output:

dbt run --select state:modified+1 --exclude staging.segment marts.segment

dbt command failed21:34:24  Running with dbt=1.6.14
21:34:25  Registered adapter: snowflake=1.6.8
21:34:25  Unable to do partial parsing because saved manifest not found. Starting full parse.
21:34:30  Encountered an error:
Runtime Error
  Expected a schema version of "https://schemas.getdbt.com/dbt/manifest/v10.json" in /tmp/defer-artifacts/manifest.json, but found "https://schemas.getdbt.com/dbt/manifest/v12.json". Are you running with a different version of dbt?

Environment

OS: Sonoma 14.4.1
Python: 3.9
dbt: 1.7

Which database adapter are you using with dbt?
snowflake
Additional Context
No response

Thanks for reaching out @mateo-persona !
Could you submit to the dbt Cloud support team via the "Create a support ticket" or "Leave feedback" button in dbt Cloud?
Link to this GitHub issue in your description. See screenshots below for an example.
Since this is specific to dbt Cloud and not dbt Core, I'm going to close this issue as "not planned" for the dbt-core repo.
Screenshots in dbt Cloud
Here's a couple screenshots of the process of leaving feedback in dbt Cloud (for this one you might choose "Create a support ticket" instead):

dbt Core v1.8 is using v12, we just need to update the docs:

https://github.com/dbt-labs/docs.getdbt.com/issues/5525


Volumio & Text to Speech

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.55.0 (Hassio)
Python release (python3 --version):
Component/platform:
Volumio
Description of problem:
Volumio doesn't play TTS files.
I’ve set up Amazon Polly. TTS-files are generated. Volumio is running. It can play music. I can interact with Volumio through Home Assistant (play, pause, volume, etc.).
Volumio can also play the TTS-files generated by Polly if I feed them to Volumio by hand. As in: starting radio and linking it to ‘https://[url-redacted]:8123/api/tts_proxy/aaf4c61ddcc5e8a2dabede0f3b482cd9aea9434d_en-us_42023311789_amazon_polly.mp3’
For Volumio to play these files, I did have to turn on audio resampling in Volumio and set bit depth to 32, and sample rate to 44.1 kHZ.
Now, when I try to use TTS with automations, or the media instance in Home Assistance, I hear absolutely nothing. (Not even some crackling, which I hear when I play non-resampled files in Volumio by hand.)
Expected:
Problem-relevant configuration.yaml entries and steps to reproduce:
# Media player Volumio
media_player:
    platform: volumio
    host: <IP_ADDRESS>
    port: 3000

# Text to speech
tts:
    platform: amazon_polly
    aws_access_key_id: xxx
    aws_secret_access_key: xxx
    region_name: 'us-east-1'
    voice: Joanna

Traceback (if applicable):
2017-10-15 11:41:55 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.6/asyncio/tasks.py", line 181, in _step
    result = coro.throw(exc)
  File "/usr/lib/python3.6/site-packages/homeassistant/core.py", line 1025, in _event_to_service_call
    yield from service_handler.func(service_call)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/media_player/__init__.py", line 408, in async_service_handler
    yield from getattr(player, method['method'])(**params)
  File "/usr/lib/python3.6/asyncio/futures.py", line 331, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.6/asyncio/tasks.py", line 244, in _wakeup
    future.result()
  File "/usr/lib/python3.6/asyncio/futures.py", line 244, in result
    raise self._exception
  File "/usr/lib/python3.6/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/media_player/__init__.py", line 707, in play_media
    raise NotImplementedError()
NotImplementedError

Additional info:

the same error,,,,how to ？

This functionality appears to be not implemented unfortunately.

Limitation seems to be due to the Volumio REST api.
Workaround:
Volumio includes MPD emulation which does support TTS from HA.  Just set up a MPD media player in HA config pointed at volumio hardware.

@brahmafear  - I tried that but I am getting nothing from volumio. What is the string to invoke this manually?

@2devnull
Here is my HA config:
`
media_player:

platform: volumio
name: kitchen_volumio
host: <IP_ADDRESS>
port: 3000

platform: mpd
name: kitchen_mpd
host: <IP_ADDRESS>
`

I can then send TTS service actions directed at media_player.kitchen_mpd.

Here is mine:
# Volumio
media_player:
  - platform: volumio
    host: <IP_ADDRESS>
    port: 3000

  - platform: mpd
    host: <IP_ADDRESS>

Can you provide an example of how to send the TTS service actions. I must be missing something on this.

For testing, I just click the three dots (see upper right red circle) then enter text in the popup window and click the icon to activate.
If you need more help, let's move this conversation out of the github issue page and over to discord.  Same username for me over there.

Thanks. I tried that also and nothing seems to be going to volumio server. I got on discord. Let me know if you can think of anything else that may be the issue.

Hey, I got it to work. My problem was I didn't realize Volumio was given a URL to a mp3 file and therefore I needed to adjust firewall to allow it.
Thanks for your help.

@2devnull I'm curios to know how you adjusted the firewall. I believe I'm running into a similar wall.
Thanks

@kjwelbeck - This was all internal firewall. I have firewall rules among VLANs and I didn't have a rule for volumio in my media VLAN to make a request to HA in my main LAN (where it is housed at the moment)


.Net: Rename GetService to GetRequiredService on the kernel

This was done in https://github.com/microsoft/semantic-kernel/pull/4046


Moved spec-gen from cmd to hack directory

Changes
Pipeline nightly https://dashboard.dogfooding.tekton.dev/#/namespaces/default/pipelineruns/pipeline-release-nightly-mk8vq?pipelineTask=publish-images&step=run-ko failed because of
ln -s /tmp/tmp.GNbmdH/source.tar.gz cmd/spec-gen/kodata/
ln: cmd/spec-gen/kodata/: No such file or directory

As we are not creating any image for spec-gen no need to have kodata folder so moved spec-gen from cmd to hack directory
/cc @vdemeester @afrittoli @jinchihe

Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ ] Includes tests (if functionality changed/added)
[ ] Includes docs (if user facing)
[ ] Commit messages follow commit message best practices
[ ] Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes

NONE

/test check-pr-has-kind-label

/retest

Ah, Good catch!
/approve

/kind misc

/lgtm


JBPM-5386 - Errai UI improvements

Removed dependency to gwtbootstrap widgets

@nmirasch please have a look :)


Fix the issue when babel presets were not found.

Folks, could you give me push access here please? Also, NPM.

@es128

@paulmillr What will it take to get source maps back in place? Also thanks so for much for tackling this issue!

@chrismccord a babel option that would allow to specify where the node_modules with babel presets are.
I suggest to use my fork of babel-brunch until folks would merge the PR in.

a babel option that would allow to specify where the node_modules with babel presets are

Is there an open issue where I can track this? I can't get a handle on their phabricator system

Is there an open issue where I can track this

We'll need to open one, yep.

Folks, could you give me push access here please? Also, NPM.

done

Have you considered setting the es2015 preset package as a peer dependency here? Might solve the problem for folks on npm 2.x.
I caution against proceeding with this PR, as it looks like it will just trade one set of users' problem with another (anyone actively using the sourcemaps).
I don't see why babel does not use require.resolve(), as that would appear to be the more proper solution, but in the meantime, I'd try out adding it as a peer dependency (possibly both peer and regular dependency simultaneously).

it looks like it will just trade one set of users' problem with another

at least folks would be able to run it. Bad sourcemaps is the least of all evils

Again, the problem is not related to npm v2. It's npm v3 too. In some cases.

Have you tried out the idea of solving this by adding the preset as a peer dependency?

A maybe related issue I am having and has been reported by others:

Use babel 2.1.1 with npm support enabled
npm install --save babel-preset-react
Receive unhelpful error

$ brunch build
06 Jan 14:12:04 - error: Initialization error - Error: ENOENT: no such file or directory, open 'path'
  at Error (native)

In desperation, I solved this issue by moving babel-preset-react to devDependencies, which still allows it to work for my usecase in Phoenix. Is this issue related? Any better fix for folks?
Example project with workaround:
https://github.com/chrismccord/phoenix_brunch_react/blob/master/package.json

@es128 npm3 removed "mandatory" peer deps. Warnings are unhelpful for users.

We will also be changing the behavior of peerDependencies in npm@3. We won’t be automatically downloading the peer dependency anymore. Instead, we’ll warn you if the peer dependency isn’t already installed. This requires you to resolve peerDependency conflicts yourself, manually, but in the long run this should make it less likely that you’ll end up in a tricky spot with your packages’ dependencies. - http://blog.npmjs.org/post/110924823920/npm-weekly-5

I disagree that it will be unhelpful, although admittedly I haven't tried it to confirm my assumptions. On npm2, where the issue is much more prevalent, the peer dependency will be installed, issue solved. On npm3, having it as both a dependency and a peer dependency should mean that it gets installed flat and suppress the warning, which also solves the problem. If the warning does occur, it tells users exactly how to solve the problem.
Under what circumstances does the problem to occur with npm3 btw? Maybe I'm not fully understanding all the situations involved.
Anyway, if you feel this is pressing you do have access now to do as you see fit icymi.

@chrismccord we're on this.

@chrismccord as babel-preset-react isn't a front-end dependency and npm for front-end integration isn't yet clever enough to actually figure out which packages are used in the front-end (in the works!), the solution for that small application would be to either whitelist the front-end packages (config.npm.whitelist = ['react', 'react-dom', ...]), or blacklist non-front-end packages (config.npm.blacklist = ['babel-preset-react', ...])

tl;dr Brunch 2.1 requires config.npm.whitelist, Brunch 2.2 would figure out the stuff automatically.

@es128 here is the issue that happens on node@3:
https://github.com/phoenixframework/phoenix/issues/1410#issuecomment-167974086
The steps to reproduce can be found here:
https://github.com/phoenixframework/phoenix/issues/1410#issuecomment-167975267
So it is not a problem of flat or tree dependencies, it is an issue of babel/brunch just looking for the dependencies in the wrong place.

@goshakkk @paulmillr ahh this makes sense. Thanks for clarify!

So actually it looks like we're looking at 2 entirely different problems at the same time.
One part is about babel's failure to use require.resolve for its plugins, which is what this PR intends to address and for which I've suggested the alternate possibility of using peerDependencies.
The other is about brunch's npm integration being somewhat manual/naive still, which @paulmillr and @goshakkk are working on improving.

Another possibility to consider is that babel-brunch > 6.0 just stops trying to work with default settings out of the box, while users are given instructions to install and specify the plugins/presets they intend to use, much like using Babel itself. Older versions could still be used and "just work"

@es128 it would solve the issue; although it's a bit non-Brunchy to expect users to install tons of plugins to just make stuff work.
 Or, autoprefixer-brunch (sadly, the owner of the repo deprecated it).
Not sure how this could work when there are more than 1 babel plugins, but sth to think about.

I'd say it's a choice Babel has made for their users. I agree it goes against what we try to do with Brunch generally. But we tried to make easy defaults, and it hasn't worked out. May be better at this point to just get out of the way and document clearly for users the steps they'll need to take.

Let's hold on this for a moment, as @josevalim may have found a nice workaround by making phoenix.js a local npm dep

We have fixed this on Phoenix by making the extra directory dependencies (at ../../deps/phoenix) simply be npm dependencies. We have added them to package.json as file dependencies and did a couple changes and now everything works! The initial PR is here: https://github.com/phoenixframework/phoenix/pull/1456
It also becomes a nice opportunity to show how the npm integration works, which is a :+1:. This would not have been possible without the work of the Brunch team on npm integration, so thank you so much.
I think we can close this issue as it no longer blocks Phoenix and losing source maps would be undesired. :)


[tutorial] broken hello-solder example board

following the guide
hello-solder project fails to build.
(pcbmode-env) user@Box:~/dev/pcbmode$ pcbmode -b hello-solder -m
-- Processing PCBmodE's configuration file
-- Processing board's configuration file
-- Creating board
Traceback (most recent call last):
  File "/home/yair/dev/pcbmode-env/bin/pcbmode", line 11, in <module>
    load_entry_point('pcbmode==4.1.dev34+ngabe96e3', 'console_scripts', 'pcbmode')()
  File "build/bdist.linux-x86_64/egg/pcbmode/pcbmode.py", line 387, in main
  File "build/bdist.linux-x86_64/egg/pcbmode/utils/board.py", line 21, in __init__
  File "build/bdist.linux-x86_64/egg/pcbmode/utils/module.py", line 58, in __init__
  File "build/bdist.linux-x86_64/egg/pcbmode/utils/module.py", line 960, in _getComponents
AttributeError: 'list' object has no attribute 'get'

Same as issue #14
I'm happy to update the doc to work for TheLady instead, as soon as my last PR gets accepted :)


Display installed plugins in "About > Version and Software Info"

PR #413 adds "plugins" for fancy language parsers (woot!).  At some point, it will be nice to include a listing of installed plugins as well.
Cases to handle:

no plugins
plugins :-)

Maybe the current hacky lute.parse.registry will need to change, separating out plugin loading from registry stuff, so that the plugins could be easily pulled out.  Or perhaps the plugin version info could be included in the registry.

Nice to have, but closing to manage the backlog.


Readme update must be updated

https://github.com/ivanseibel/next-js-shop/commit/ff8bef29df4f33793a5986b90764e9c4a86a7963


No way to define band selection per SSID using API

Meraki has recently introduced (around Oct 12th) a new way to handle band selection per SSID in the GUI.
Before this change:

RF profile contained a toggle to indicate that band selection is defined 'per SSID' or for 'all SSIDs'
when toggle was set to 'all SSIDs' the value common to all SSIDs (2.4Ghz or 5Ghz or both) was defined within RF profile
when toggle was set to 'per SSID', the value for each SSID was defined within SSID settings

In order to handle 'per SSID' case with API, one had to use:

wireless.createNetworkWirelessRfProfile() or wireless.updateNetworkWirelessRfProfile() to set the toggle to 'per SSID'
wireless.updateNetworkWirelessSsid() for each SSID to set its band selection value

This was working fine, I had prepared a script (using library 1.12.0) to perform harmonization of band selection settings across 400 networks worlwide.
After the  change:
All band selection settings are managed within RF profile i.e. for both 'all ssids' (as before) and for 'per SSID' (new).
From an ergonomy point view, this change is a good thing because all information about band selection 'per SSID' are gathered into a single GUI page (RF profile definition), instead of several pages (RF profile for toggle setting, and Access Control page of each SSID).
However, the issue is that API has not been modified to reflect the change in GUI / data structure related to band selection.
wireless.createNetworkWirelessRfProfile() or wireless.updateNetworkWirelessRfProfile():

are still allowing to set the toggle 'all SSIDs' / 'per SSID'
are still allowing to set the common value to 'all SSIDs'
BUT they are not allowing to define one value per SSIDs

My request is to add a calling argument to these endpoints to define band selection setting of one or several SSIDs.
This would restore the possibility to handle 'per SSID' case using API.
Remark :
wireless.getNetworkWirelessRfProfile() is correctly providing 'per SSID' settings that have been defined using new version of the GUI.
Result of this endpoint now contains a new key named 'perSsidSettings' whose value is a dictionnary which contains 15 keys (one per SSID) with the following structure
'ssidNumber' : {'name' : 'nameofSSIDnumber', 'minbitrate' : xx, 'bandOperationMode' : 'dual|5Ghz|2.4Ghz', 'bandSteeringEnabled' : True|False}
This same structure could be used to set value when calling create or update endpoints.
The dictionary passed in argument could contains a definition for each ssid number (0 to 14), or only for a subset of those numbers ==> only those numbers would be updated
Before updating the values for a given ssid number, a consistency check based on 'name' key must be implemented.
If 'ssidNumber' and 'name' are not in accordance, then an error is returned.

Latest version of the library (v1.15.0) is still exhibiting the same issue.
Said otherwise, 3 munths later the issue has not been corrected.
Is there any possibility to increase the priority of my request ?

Now available in library version 1.18.2.


Initial webpage

TO DO:

Find a name for the project
Write a decription for the project
Design of the webpage

Is it ready for submission? I see empty page

Find a name for the project
Write a decription for the project
Design of the webpage

Is it the django landing page?

Not ready. just an initial one to update

Please Mark it as draft,
Please refer this link
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request

Good Job! 🥇 Our next mission is to run it as the index.html page of Django.
Let's do it in another PR. (Or maybe we should rebase this PR on the main and continue contributing on this PR? @Yarboa @kasemAlem what do you think is the correct way?)
I can make an issue for guidance.

@amittcohen I made a new issue for you at #15

In the last commits:

Added the webpage to the django application following the instruction in part 5 of the tool introduction challenge.
Removed the downloaded css files and put a link instead as requested.


First Timers Only

Contributing to open source for the first time can be scary and a little overwhelming.
I'm willing to hold your hand so you can make your first PR. The tasks mentioned in this issue are rather a bit easier than normal. And anyone who's already contributed to open source isn't allowed to touch them!
Okay, here we go! The aim of this project is to extend http://github.com/swapagarwal/JARVIS-on-Messenger functionalities to other platforms (like Telegram). Head over to http://m.me/J.A.R.V.I.S.on.Messenger and try out the features. Pick any one simple feature and we'll add it to https://t.me/jarvis_chatbot
Join the conversation on Discord: https://discord.gg/MsZ9N9n 👈
I'd highly encourage you to document the process, blog and tweet about it and encourage other first timers to do the same!
https://www.firsttimersonly.com/

Hello! We are 2 students from the computer science department of Aristotle University of Thessaloniki and we want to work on that for a project we have on open source.

@StylPamp Let's discuss more on Discord. 👍

Hi I am also student from india , and would like to contribute in your project

@Predator1997 Hop on to Discord and we'll pick what you can work on. 👍

Thanks for letting me help, can i know your discord username?
Thank You
Parth Bangale
On Thu, Dec 13, 2018 at 7:20 AM Swapnil Agarwal<EMAIL_ADDRESS>wrote:

@Predator1997 https://github.com/Predator1997 Hop on to Discord and
we'll pick what you can work on. 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/the-vision/jarvis-telegram/issues/1#issuecomment-446812530,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ab2v0plhhvUSr_CfEZGygf_rVgX3NXTXks5u4bJbgaJpZM4ZNrPR
.

Join the conversation on Discord: discord.gg/MsZ9N9n 👈

☝

Hey, I'd love to contribute to the project. This would be my first time.

Hi @swapagarwal , I would love to contribute to the project. Please let me know how can I get on?

hello..im mew to coding..(python)..been doing it about a yeat now...is this the right place for me?

Hi there! I’m interested in contributing! Should I just message you on discord so we can talk about how I could contribute? I’ve never contributed to an open source project before

Hello! I would love to contribute to this open source project. Let me know what I should work on. Thanks!

@swapagarwal
Is this still open for contribution? I am rather new to Python and have never contributed to Open Source before. It would be great if I could start here. Any suggestions?

Hi there, I am also very new to Python and have never contributed. I would love to start here or get any suggestions!
Many thanks,
Madeline

Hi There!,
I'd like to contribute to this project, I'm quite new to open-source, is there a discord I can join?

Hi, I am new to open source and would like to contribute to this ticket. Can you please let me know if this this ticket is still open?

Hi, I am new to open source and would like to contribute to this ticket. Can you please let me know if this this ticket is still open?

Hello Swapnil, I am new to GitHub and would like to contribute as part of my college project. Is it still open, or would you recommend other projects that do the same?

Contributing to open source for the first time can be scary and a little overwhelming. I'm willing to hold your hand so you can make your first PR. The tasks mentioned in this issue are rather a bit easier than normal. And anyone who's already contributed to open source isn't allowed to touch them!
Okay, here we go! The aim of this project is to extend http://github.com/swapagarwal/JARVIS-on-Messenger functionalities to other platforms (like Telegram). Head over to http://m.me/J.A.R.V.I.S.on.Messenger and try out the features. Pick any one simple feature and we'll add it to https://t.me/jarvis_chatbot Join the conversation on Discord: https://discord.gg/MsZ9N9n 👈
I'd highly encourage you to document the process, blog and tweet about it and encourage other first timers to do the same! https://www.firsttimersonly.com/

Hey, I'm beginner. I use ChatGPT to find an open-source project. I hope I'm in the right place.


Error in README.md

In the just released new version of the README.md you say under Linux and Android
... by choosing graalvm-ce-java11-darwin-amd64-20.2.0-dev.tar.gz. I doubt this is correct. This should probably be graalvm-ce-java11-linux-amd64-20.2.0-dev.tar.gz.

Thx, good catch, fixed.


Audit CI scripts and Yaml for unwanted exit code clobbering

I wonder how we could avoid accidentally clobbering the exit code in the future. We should probably do an audit of other instances of || echo in our CI scripts and Yaml files.

Originally posted by @dmcardle in https://github.com/lowRISC/opentitan/issues/14668#issuecomment-1232964502

When I filed this issue, I was thinking of explicit exit code clobbering with boolean-or, e.g. foo || echo blah, where foo fails, but the script continues due to the successful echo.
Another way to clobber exit codes is with bash pipelines, e.g. foo | bar.  This was an issue in https://github.com/lowRISC/opentitan/pull/14343#discussion_r961788476 and the solution was to set -o pipefail.


Support adding Reviewers or Assignees by email instead of an Id

The current configuration for Reviewers or Assignees is quite cumbersome.
As described in #543 required to configure some cryptic ID numbers in the dependabot.yml.
This PR enables the configuration of email addresses, which is much more aligned with the dependabot config description.
this now allows the configuration:
version: 2
updates:
  - package-ecosystem: "nuget"
    directory: "/"
    # Add assignees
    assignees:
      -<EMAIL_ADDRESS>      -<EMAIL_ADDRESS>
internally the email addresses are resolved and the ids are passed to dependabot for creating the PR.

I don't think there's a need to change the updater. The extension can fetch the user identifier from the API and form a JSON array as is expected. That way it doesn't break current functionality.
I'd rather check each entry to find if it is an email (e.g. check it contains an @) to determine if it is an email or an ID. You could choose to do the reverse by parsing as a GUID.
The changes need to be effected server side too.
Please add tests for the changes unless.

I will look into it

is mainly for logging the Reviewers and Assignees in clear text, but can be omitted.
how would you do that? Via regular expression ? I wanted to make it fast (faster than regex) and the "fallback" is always assumed as a UUID no @ should be part of it, see here.
I did not got this point, which changes needs to be done server side? Can you give me a hint here?
Which parts would you focus on in the tests? The point that emails are handled differently that other input strings?

@mburumaxwell did you had a chance to review this?

@BobSilent could you resolve the conflict so I can merge?

Sure, I will take care here.

@mburumaxwell: rebased the PR

As soon as I add a reviewers or assignees field in my config, my pipeline throws: "##[error]Cannot read properties of undefined (reading 'length')".
this is my pipeline:
trigger: none # Disable CI trigger

schedules:
  - cron: '0 2 * * *' # daily at 2am UTC
    always: true # run even when there are no code changes
    branches:
      include:
        - master
    batch: true
    displayName: Daily

stages:
  - stage: CheckDependencies
    displayName: 'Check Dependencies'
    jobs:
      - job: Dependabot
        displayName: 'Run Dependabot'
        pool:
          vmImage: 'ubuntu-latest' # Only Ubuntu and MacOS is supported at this time
        steps:
          - task: dependabot@1
            displayName: 'Run Dependabot'

and my dependabot.yml:
version: 2
updates:
  - package-ecosystem: "npm"
    directory: "/"
    schedule:
      interval: "daily"
    open-pull-requests-limit: 50
    reviewers:
      - "<email>"

Any idea what could be going wrong?


\newcommand*{} not supported

It would be nice if the starred version  \newcommand*{} could be supported, which does not seem to be the case at the moment.

You are right, this isn't supported right now. Should be an easy thing to do. I try to take care of it soon.

Should be fixed now. Please let me know, if it does not work as expected.

Thank you for the fix. If the command doesn't have any arguments, then it is indeed working now.
However, if there are arguments such as \newcommand*{\echoargument}[1]{#1} then in the main text the \echoargument{text} would be replaced by #1 (while one would expect text). The same would be the case for the unstarred version, \newcommand{\echoargument}[1]{#1}.

Interesting. Don't know why I didn't have a test case for that. Will fix it some day soon.

Finally found some time to fix it. Lost some time with it because I forgot that LaTeX-commands cannot have any numbers (and I did tests with commands like \test1{}). Should be working now, but I could only do some quick checks. I have to do some more extensive use of the tool myself soon, so potentially I will notice further bugs then.


Diamond does not yet support Python 3

I've been informed that diamond does not yet support Python 3.

Thanks!


Set the license on the release detail page.

This branch includes a modification to the release detail page to replace the license TODO with the Release.license attribute.
I removed the hyperlink because license is an unstructured text field from distutils and it's not possible to exactly determine what the URL of that field might be (e.g., the code might be able to guess the correct license URL for "BSD", however, "Project X custom license" would not be feasible to provide a license URL).
The one aspect that I did not know how to handle was the case of a missing license. My thought was to put some default value like UNKNOWN in that spot. I'm happy to do that, but I don't know how to set l20n so that it will know how to deal with a default value.
As this is my first contribution to this project, I'd appreciate any feedback if I'm missing something important. Thanks! :smile:

I've been poking around the issues page and found that this fix is probably insufficient (who would have thought that some people would put entire license text into that field!).
I'm still very open to helping make this a useful branch and can work on the necessary changes.
My initial thought that comes to mind is to display only the first line of text of the Release.license field contains multiple lines.
Something else to consider would be favoring an existing license Trove classifier over the Release.license field if the classifier exists. Maybe the display of the classifier would be as the right most segment (e.g., BSD License from License :: OSI Approved :: BSD License).

@mblayman I'm of the mind to just ignore the license field and only use classifiers.. or maybe if there's no classifiers and the license field contains some text, add a link that says "Other" and opens up a modal dialog with the content of the license field or something.
Maybe @nlhkabu has a better idea.

@nlhkabu, I tried to write the code in a way that it will take the classifier if it exists. While it does always attempt to take the license metadata first, the presence of a classifier will always override the metadata value.
I'll make sure it does that. Looks like I need to add another test for additional code coverage anyway.

I updated a test case to a) boost coverage and b) show that a classifier is preferred over license metadata. I hope this clears things up.

So we have a couple of open questions here in my mind.

Is the Release.license field reasonably formatted in enough cases to stick it sort of free form in the top of the page where the License information should go?
If we're going to use both Release.license and classifiers, what should we do when something contains both of them?
What if something contains multiple licenses?

Personally for myself I'm thinking:

I think that there's just junk data here to realistically pull meaning information out of it. We have values ranging from a handful of characters to over 32,000 characters in the database. I'm thinking at most we should render this somewhere else (maybe another tab on the side? I don't know) or not at all.
Given my feelings on (1), this question becomes moot.
I think we should include all of the license classifiers, not just the first one.

One idea that's kind of sticking in my head though, is I wonder if it'd make sense to try and translate the classifiers to SPDX License language? Perhaps an even further idea is to repurpose the license field to be defined as a SPDX License Expression and have PyPI validate that, for all new packages, that field contains only valid license expressions. Then we could have the tag at the top be license expressions which for the most common cases will just be short names for each licenses, but can also easily represent more complex cases like "GPLv2 or later", "BSD OR Apache", "BSD AND Apache", or even GPLv2 or later with the Bison 2.2 exception". If we did that we could link each class in the expression to the canonical location for that license and I think it'd end up being real nice.
What do folks think about that?

Those are good questions @dstufft.

I presume that the Release.license is reasonably formatted for some cases. I wrote the code to grab the first line in case the content is not reasonable. I don't believe that any solution using Release.license will display perfectly, however, displaying the first line seemed like a reasonable compromise to me.
As implemented, if both Release.license and a license classifier exist, this branch will always choose the license classifier. That seemed like the right thing to do because the classifiers have a good level of consistency.
I did not account for multiple licenses in this branch so far. I can certainly update the branch to collect license classifiers into a list and then return a joined version. In that case, a packaging containing License :: OSI Approved :: BSD License and License :: OSI Approved :: GNU General Public License v2 or later (GPLv2+) could produce an output of BSD License, GNU General Public License v2 or later (GPLv2+).

While SPDX seems interesting, I suspect that repurposing the existing Release.license field would cause some backwards compatibility trouble. The SPDX list is limited, and if authors are given no option to provide whatever license they choose, it seems like PyPI would place an unnecessary restriction on them. While I personally feel that uploading a package with a non-standard open source license is foolish, I lean toward openness for packages that may exist in unusual circumstances and need unusual licenses.

From a UI perspective, I'm not keen on moving the license to a separate tab - given the content could be just a few words, I think there is a risk it is going to look really odd.
I think we should move license to the bottom of the header (e.g. under the 'pip install box').  This will allow for longer strings - including multiple licenses as @mblayman describes in point 3.
For any licenses that are truncated after the first line, we can add a 'read more' link that launches the full thing in a modal (yes, Donald, I've come around to your thinking on the modal :P ).
For launch I can probably live without the modal being done (with just the truncated text showing)- we should open a separate issue for this.

This branch is now updated to support multiple license classifiers. I took @nlhkabu's advice and moved the license label so that it is below the pip install <package> portion. I agree with her sentiment of doing the modal and "Read more" work later and tracking it with a separate issue.

They code changes here look reasonable to me, if @nlhkabu is happy with the UI changes (or if she plans on adjusting it herself) this looks fine to merge to me.

@mblayman are you able to provide me with a screenshot so I can verify this visually?

Sure thing.

Thanks @mblayman - in the short term, can you please remove the right alignment.  If I need to adjust the margins, I can do so when I make other updates to this section :)

All set.

:sparkles: :tada:

Sweet! Thanks for all the feedback along the way. It feels nice to be able to contribute a small bit back to a community that I've been working in for years.


Any client calls results in error

I have pulled down the repo, ran a rebuild and then referenced the built dll into a .net framework 4.8 project.
Added this is as test:
           var client = new HttpClient();
            var pokiclient = new PokeApiClient(client);
            var xx = pokiclient.GetResourceAsync<Pokemon>("ho-oh").Result;

And currently get this error:
System.IO.FileNotFoundException: 'Could not load file or assembly 'Microsoft.Extensions.Caching.Memory, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60' or one of its dependencies. The system cannot find the file specified.'
This happens in the resource cache manager here:
        /// <summary>
        /// Constructor
        /// </summary>
        public ResourceCacheManager()
        {
            // TODO allow configuration of experiation policies
            _resourceCaches = ResourceTypes.ToImmutableDictionary(x => x, _ => new ResourceCache());
        }

I have tried other client methods and all result in the same error

Does the same error happen when the nuget package is used instead of the dll? I suspect this is due to differences in how dependencies are resolved between nuget packages and dll files.

Yeah, that was the exact issue, building it from the source it was missing dependencies which nuget handles all for you, my bad!


[Bug]: using shareFilesWithResult to share both file and text to WhatsApp, file is not shared

Platform
iOS 15.5
Plugin
share_plus
Version
4.0.10+1
Flutter SDK
3.0.3
Steps to reproduce

save screenshot image to file
String imagePath = PhoneAppDirectory.root + '/screenshot.jpg';
await File(imagePath).writeAsBytes(mergedImageBytes);
share the image and a string
var result = await Share.shareFilesWithResult([imagePath],
text: strHashTag']
);
if the share is successful, save it to phone gallery
if ( result.status == ShareResultStatus.success ) {
await ImageGallerySaver.saveImage(imageBytes as Uint8List, quality: 100);
}

This works fine when sharing to other app (Facebook, mail, etc.). However, when sharing is to WhatsApp, only the text string is shared.
Please let me know if this is a bug or a feature not yet implemented. Thank you
Code Sample
var result = await Share.shareFilesWithResult([imagePath],
          text: 'My memory',
     );

Logs
2022-08-27 14:53:49.026350+0800 Runner[5275:6248424] flutter: findRenderObject: 0
2022-08-27 14:53:49.868671+0800 Runner[5275:6248424] flutter: boundary.toImage : 841
2022-08-27 14:53:49.972143+0800 Runner[5275:6248424] flutter: img.decodePng: 103
2022-08-27 14:53:50.189320+0800 Runner[5275:6248424] flutter: build image to share: 217
2022-08-27 14:53:50.190177+0800 Runner[5275:6248273] [Default] Task Runner[5275]/1#6 LF=0 couldn't find entitlement CopresenceCore.Entitlement.publicAPI error nil
2022-08-27 14:53:50.199829+0800 Runner[5275:6248273] [Default] Task Runner[5275]/1#6 LF=0 couldn't find entitlement CopresenceCore.Entitlement.publicAPI error nil
2022-08-27 14:53:50.317164+0800 Runner[5275:6248273] [default] LaunchServices: store (null) or url (null) was nil: Error Domain=NSOSStatusErrorDomain Code=-54 "process may not map database" UserInfo={NSDebugDescription=process may not map database, _LSLine=264, _LSFunction=-[_LSDReadClient getServerStoreWithCompletionHandler:]}
2022-08-27 14:53:50.317194+0800 Runner[5275:6248273] [default] Attempt to map database failed: permission was denied. This attempt will not be retried.
2022-08-27 14:53:50.317215+0800 Runner[5275:6248273] [db] Failed to initialize client context with error Error Domain=NSOSStatusErrorDomain Code=-54 "process may not map database" UserInfo={NSDebugDescription=process may not map database, _LSLine=264, _LSFunction=-[_LSDReadClient getServerStoreWithCompletionHandler:]}
2022-08-27 14:53:50.317987+0800 Runner[5275:6248273] [default] -imageForImageDescriptor: can do IO please adopt -imageForDescriptor: for IO free drawing or -prepareImageForDescriptor: if IO is allowed. (This will become a fault soon.)
2022-08-27 14:53:50.324438+0800 Runner[5275:6248273] [LayoutConstraints] Changing the translatesAutoresizingMaskIntoConstraints property of a UICollectionReusableView that is managed by a UICollectionView is not supported, and will result in incorrect self-sizing. View: <_UIActivityContentFooterView: 0x12fd8df30; baseClass = UICollectionReusableView; frame = (16 638.333; 358 52); layer = <CALayer: 0x280c966a0>>
2022-08-27 14:53:50.383543+0800 Runner[5275:6248273] <CATransformLayer: 0x280c19d60> - changing property backgroundColor in transform-only layer, will have no effect
2022-08-27 14:53:50.405050+0800 Runner[5275:6248273] [LayoutConstraints] Unable to simultaneously satisfy constraints.
	Probably at least one of the constraints in the following list is one you don't want.
	Try this:
		(1) look at each constraint and try to figure out which you don't expect;
		(2) find the code that added the unwanted constraint or constraints and fix it.
(
    "<NSLayoutConstraint:0x282f7ce60 _UIActivityActionCellTitleLabel:0x12fdb5830.height >= 22   (active)>",
    "<NSLayoutConstraint:0x282f7e1c0 UIView:0x12fd9f230.height >= _UIActivityActionCellTitleLabel:0x12fdb5830.height + 30   (active)>",
    "<NSLayoutConstraint:0x282f6e210 'UIView-Encapsulated-Layout-Height' UIView:0x12fd9f230.height == 30   (active)>"
)

Will attempt to recover by breaking constraint
<NSLayoutConstraint:0x282f7ce60 _UIActivityActionCellTitleLabel:0x12fdb5830.height >= 22   (active)>

Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful.
2022-08-27 14:53:50.405336+0800 Runner[5275:6248273] [LayoutConstraints] Unable to simultaneously satisfy constraints.
	Probably at least one of the constraints in the following list is one you don't want.
	Try this:
		(1) look at each constraint and try to figure out which you don't expect;
		(2) find the code that added the unwanted constraint or constraints and fix it.
(
    "<NSLayoutConstraint:0x282f67cf0 _UIActivityActionCellTitleLabel:0x131e25cb0.height >= 22   (active)>",
    "<NSLayoutConstraint:0x282f67b10 UIView:0x131e0f8f0.height >= _UIActivityActionCellTitleLabel:0x131e25cb0.height + 30   (active)>",
    "<NSLayoutConstraint:0x282f6e940 'UIView-Encapsulated-Layout-Height' UIView:0x131e0f8f0.height == 30   (active)>"
)

Will attempt to recover by breaking constraint
<NSLayoutConstraint:0x282f67cf0 _UIActivityActionCellTitleLabel:0x131e25cb0.height >= 22   (active)>

Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful.
2022-08-27 14:53:50.405593+0800 Runner[5275:6248273] [LayoutConstraints] Unable to simultaneously satisfy constraints.
	Probably at least one of the constraints in the following list is one you don't want.
	Try this:
		(1) look at each constraint and try to figure out which you don't expect;
		(2) find the code that added the unwanted constraint or constraints and fix it.
(
    "<NSLayoutConstraint:0x282f97930 _UIActivityActionCellTitleLabel:0x13564a620.height >= 22   (active)>",
    "<NSLayoutConstraint:0x282f95590 UIView:0x135649740.height >= _UIActivityActionCellTitleLabel:0x13564a620.height + 30   (active)>",
    "<NSLayoutConstraint:0x282f6da90 'UIView-Encapsulated-Layout-Height' UIView:0x135649740.height == 30   (active)>"
)

Will attempt to recover by breaking constraint
<NSLayoutConstraint:0x282f97930 _UIActivityActionCellTitleLabel:0x13564a620.height >= 22   (active)>

Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful.
2022-08-27 14:54:03.699964+0800 Runner[5275:6248273] [NSExtension] Extension request contains input items but the extension point does not specify a set of allowed payload classes. The extension point's NSExtensionContext subclass must implement `+_allowedItemPayloadClasses`. This must return the set of allowed NSExtensionItem payload classes. In future, this request will fail with an error.
2022-08-27 14:54:08.424678+0800 Runner[5275:6248273] [core] SLRemoteComposeViewController: (this may be harmless) viewServiceDidTerminateWithError: Error Domain=_UIViewServiceErrorDomain Code=1 "(null)" UserInfo={Terminated=disconnect method}
2022-08-27 14:54:08.950197+0800 Runner[5275:6255468] [ShareSheet] connection invalidated

Flutter Doctor
ios$flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.0.3, on macOS 12.5.1 21G83 darwin-arm, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.1)
[✓] Connected device (3 available)
[✓] HTTP Host Availability

I just found other posts about the same issue, will close it now.

https://github.com/fluttercommunity/plus_plugins/issues/645

https://github.com/fluttercommunity/plus_plugins/issues/730

@moxran  how did you fix ?


There is no checkpoint output,

Thanks for your contribution, and after train, i get nothing, no checkpoint, why?
`----------------------------
| grad_norm     | 0.00858  |
| lg_loss_scale | 20.9     |
| loss          | 0.00124  |
| loss_q0       | 0.00374  |
| loss_q1       | 0.000934 |
| loss_q2       | 0.00063  |
| loss_q3       | 0.000106 |
| mse           | 0.00124  |
| mse_q0        | 0.00374  |
| mse_q1        | 0.000934 |
| mse_q2        | 0.00063  |
| mse_q3        | 0.000106 |
| param_norm    | 240      |
| samples       | 4e+05    |
| step          | 5e+04    |
saving model 0...
saving model 0.9999...`

Take a look at how I'm training mine, I'm getting a model output with this configuration...
!LOGDIR="OUTPUT/sinddpm-yourimage-day-commitseq" python image_train.py --data_dir /content/upscaled2.png --lr 5e-4 --diffusion_steps 1000 --image_size 256 \
                                   --noise_schedule linear --num_channels 64 --num_head_channels 16 --channel_mult "1,2,4" \
                                   --attention_resolutions "2" --num_res_blocks 1 --resblock_updown False --use_fp16 True \
                                   --use_scale_shift_norm True --use_checkpoint True --batch_size 16

Hope this helps!

It seems that bash: !LOGDIR="OUTPUT/sinddpm: event not found. Is that true?

It has been sovled, thanks for a lot

No problem

@zhangbaijin May I ask how did this problem solve? I meet with the same problem. Thanks.

Hi @dillfrescott, I used the same code as yours and the size of my input image is 256x256. But I got an error called RuntimeError: Sizes of tensors must match except in dimension 1. Expected size 54 but got size 53 for tensor number 1 in the list. Could you help me resolve this issue? Thank you in advance!

Hi @dillfrescott, I resolved the problem just now by adding \ after each line. But I wonder if you know how many steps the training process takes in total. Thank you.

@KevinWang676 It's been a while since ive used this project. I'm glad you were able to fix it though but I do not remember how many steps the training process takes in total.

It has been sovled, thanks for a lot

Hello, may I ask how many steps did you train to complete the training？


x/tools/gopls: limit number of returned completions (maybe just unimported)

With unimported completions on, triggering completions with no prefix is very slow. Depressingly, the main problem is generating the diffs for all the imports that could be added -- after https://golang.org/cl/205678, we need to do some fairly expensive parsing and formatting for each one. Profile:

There's really no point in returning every single package in the module cache as a completion candidate. I think we should definitely limit those.
I think @muirdm has also said that Emacs may have trouble handling large numbers of completions regardless. So maybe we should just put a cap on the entire result set?

If I remember correctly, I was referring to a massive amount of candidates slowing gopls down rather than client side issues.
I feel like at this point we have enough per-candidate work it might make sense to change to the "resolveCompletion" approach where we defer work until the user selects the candidate. This would include deferring looking up the docs and computation of any edits. It also opens the door for the "I'm feeling lucky" improvement where placeholder snippets come pre-populated with the top completion candidate(s).
For this particular case we could also cache the edits per unimported package rather than computing them for every candidate (i.e. wasteful if you have 100 candidates from the same unimported package).
Regardless of performance issues, though, I also think there are too many unimported package completions to be useful (I'm talking about the package name completions, not the package member completions). We could use stricter matching such as requiring an exact prefix match for the first N characters in the package name. If the package list is sorted usefully beyond just the location of the package (i.e. by import frequency), then dropping all but the top N unimported packages may also be a good option.
Arbitrarily limiting the overall completion response may also be good. I don't think I have ever scrolled through 50 candidates just to select the 51st candidate. The key is limiting candidates before we have done all the work to create the candidates. Note that this only works when we are doing server-side filtering. If the user disables gopls fuzzy matching and deep completions we still need to return all the candidates since the editor performs further filtering.

I agree with everything above, though I am nervous about using completionItem/resolve. I should dig up an old CL that I had to implement it, but I remember I found it made completion "feel" slower because it always gets triggered for the first completion candidate. So then, a single textDocument/completion request becomes a textDocument/completion + completionItem/resolve. I'm not sure how to avoid this, though.

So then, a single textDocument/completion request becomes a textDocument/completion + completionItem/resolve

Can we can pre-resolve the top N candidates so it is only slow if they scroll? Maybe put in a special data cookie to make the "resolve" action a  no-op.

That sounds like a good start. We should test if that approach still "feels" slower because of the extra round trip. Let me find that CL so we can start working on this...I think it must have been when I was adding completion documentation.

I'm not sure if this is still useful, but here was my implementation of completionItem/resolve from July :smile:. It's only on patchset 5 because after that I changed my mind (CL 184721).

@muirdm I'm not too familiar with this area and I don't want to spend a ton of time on it right now. Do you want to do something soon? If not, I'll probably just cap completions at 50 or whatever and we can do something more sophisticated later.

Out of curiosity, are you referring to capping the final completion list, or just some aspects of it?
I know that completions (at least with my experience with VS Code + LSP) will do things like "send one completion request after the ., then filter it on what the user continues to type without re-requesting the completion". Does gopls do some trick to prevent that behavior and always be able to provide a new completion list at the cost of needing more calls?

Something simple for now sounds good to me.
Unsolicited thoughts, but capping the unimported packages will be simplest assuming you can just take the first N matching packages and then stop.
To cap all candidates you need to take the top N highest scorers, so you would probably need a heap or similar data structure to efficiently track the top N highest scoring candidates as we find them. Or maybe just defer the per-candidate work until after sorting and capping, but that probably isn't too easy either.

Does gopls do some trick to prevent that behavior and always be able to provide a new completion list at the cost of needing more calls?

Yes, we set the "incomplete" flag in the completion results which makes the editor re-request completions after every keystroke. This behavior is required for server side fuzzy matching and deep completions.


Add freebsd support: Add MAP_FIXED to mmap call.

The codeblock fails on freebsd unless MAP_FIXED is explicitly set.

Thanks, I didn't test on freebsd. I think, we could (should?) also use MAP_EXCL on freebsd to make sure, we don't mess with existing mappings. What do you think? Since we unmap the second half before, we shouldn't interfere with existing mappings, if everything goes as planned. https://man.freebsd.org/cgi/man.cgi?mmap(2)


Adding Share to facebook button

Adding Share to facebook button.

@swapagarwal Shall I close this PR without merging if it doesn't interest you?

Hi! I didn't get a chance to review this. Will do tonight! 😇
…
---- On Mon, 08 Oct 2018 15:50:28 +0530<EMAIL_ADDRESS>wrote ---- @swapagarwal Shall I close this PR without merging if it doesn't interest you? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

"Tonight"

@AndyIsHereBoi sorry the project was ded, but not now!

But sadly after you PR we had many changes to project. It would be great if you update the PR.


hidpp20 led capabilities

Grab the capabilities from the device where possible instead of just assuming we have them.
I'm not 100% sure I read the monochrome-only effects bit right, @SonicFrog please confirm that bit, thanks.

It's not in the info flag but you can run ratbactl led 1 capabilities. Maybe not the best interface :)


add mp3 extension to voicemail url

this will allow web browsers to play inline and media players to easily recognize as media file.

Can you add more detail here?

currently clicking on the play link to listen to a voicemail opens up a open file dialog box from a file linked like so https://api.twilio.com/2010-04-01/Accounts/ACd10fthgdhfgh3fba730884154/Recordings/REd23962befdghfhsgfdac3409667cdb4d with this file not having an extension a web browser does not know what to do with it. adding the mp3 extension will ease this problem. you could also add a .wav extension but this adds no benefit what so ever. (audio quality and sample rate its recorded at is really low)

Missing release notes and version bump.


npalamar / create background chat image and fix some ui bugs

Created backgound image for chats with corresponding logic

Set navigation bar, tab bar translucent to NO;
Fix some ui bugs when screen rotares;
Now width depends on screen widht (width * coefficient)
Remove code for hiding separator line in Frieds VC
Add tableView footers with zeroFrame for removing unusefull lines

I have some problems with images and i guess i'll solve them this week

It doesn't build. It seems that you've removed all toxcore files in last commit bfbe2c1.
After some thoughts I decided that we don't need background images in Antidote (at least for now). Almost any image kills color scheme. Image doesn't fit bubbles and buttons color, messages became less readable. Really, it looks like a mess and I don't think it is a good user experience.

However launch images and bug fixes are okay. Can you make another pull request with it?
Thank you for your work. Please, don't make such complicated pull requests in the future. One thing at once would be much better.

Hi! Yes I can next week. I'll split this branch into two another branches, first branch will contain bug fixes and launch images, second will contain chat background images functionality (may be in the future it will have sense).


I have a TypeError with the latest version

I run: pykwalify -d data.yaml -s schema.yaml
I get:
Traceback (most recent call last):
  File "/usr/local/bin/pykwalify", line 11, in <module>
    sys.exit(cli_entrypoint())
  File "/usr/local/lib/python2.7/dist-packages/pykwalify/cli.py", line 84, in cli_entrypoint
    run(parse_cli())
  File "/usr/local/lib/python2.7/dist-packages/pykwalify/cli.py", line 71, in run
    c.validate()
  File "/usr/local/lib/python2.7/dist-packages/pykwalify/core.py", line 147, in validate
    self._start_validate(self.source)
  File "/usr/local/lib/python2.7/dist-packages/pykwalify/core.py", line 192, in _start_validate
    self._validate(value, root_rule, path, done)
  File "/usr/local/lib/python2.7/dist-packages/pykwalify/core.py", line 211, in _validate
    self._validate_mapping(value, rule, path, done=None)
  File "/usr/local/lib/python2.7/dist-packages/pykwalify/core.py", line 484, in _validate_mapping
    self._validate(v, r, u"{}/{}".format(path, k), done)
  File "/usr/local/lib/python2.7/dist-packages/pykwalify/core.py", line 213, in _validate
    self._validate_scalar(value, rule, path, done=None)
  File "/usr/local/lib/python2.7/dist-packages/pykwalify/core.py", line 560, in _validate_scalar
    res = re.match(rule.pattern, value, re.UNICODE)
  File "/usr/lib/python2.7/re.py", line 141, in match
    return _compile(pattern, flags).match(string)
TypeError: expected string or buffer

data.yaml:
d: 1

schema.yaml:
type: map
mapping:
    d:
        type: str
        pattern: '[0-9]+'
        required: true

With the version 1.5.1 I get what I expected:
 ERROR - validation.invalid
 ERROR -  --- All found errors ---
 ERROR - [u"Value '1' is not of type 'str'. Path: '/d'"]
Traceback (most recent call last):
  File "/home/sbrunner/.py/bin/pykwalify", line 11, in <module>
    sys.exit(cli_entrypoint())
  File "/home/sbrunner/.py/local/lib/python2.7/site-packages/pykwalify/cli.py", line 84, in cli_entrypoint
    run(parse_cli())
  File "/home/sbrunner/.py/local/lib/python2.7/site-packages/pykwalify/cli.py", line 71, in run
    c.validate()
  File "/home/sbrunner/.py/local/lib/python2.7/site-packages/pykwalify/core.py", line 159, in validate
    error_msg=u'.\n - '.join(self.validation_errors)))
pykwalify.errors.SchemaError: <SchemaError: error code 2: Schema validation failed:
 - Value '1' is not of type 'str'. Path: '/d'.: Path: '/'>

My analysis is that the _validate_scalar_type will just add an error (don't stop), than this commit add the issue https://github.com/Grokzen/pykwalify/commit/f6c744fac3ca56455ec1b68ff19828ba13fdfb75

For my the pattern shouldn't be test if the type is wrong ...

Closing this one after merged #80. See PR for more details.


Cannot start cassandra docker container on mesos/mrathon

Hi,
I've been using this blog post: http://revise.ly/en/using-apache-mesos-docker-production/ to setup cassandra containers on mesos/marathon.
When i submit the first son to create a cassandra container, it shows up as "deploying" on the marathon UI. But nothing happens. Do you know if there have been any updates that i am not aware of?
any help would be appreciated!
Thanks!

UPDATE: I was able to get the first node running, but when i run the second json to connect with the SEED, it exists with the error:
Container '48422628-7a85-4f8a-8d47-0833386659cc' for executor 'cassandracluster.1ee32629-c84c-11e4-b9cd-089e0150898e' of framework '20150304-161802-1420689674-5050-25118-0000' failed to start: Failed to 'docker run -d -c 1024 -m 536870912 -e PORT_9042=9042 -e PORT_7199=7199 -e MARATHON_APP_VERSION=2015-03-11T23:56:05.459Z -e HOST=svdpdac017.techlabs.accenture.com -e PORT_9160=9160 -e PORT5=8012 -e CASSANDRA_TOKEN=1 -e CASSANDRA_SEEDS=<IP_ADDRESS> -e PORT4=9042 -e MESOS_TASK_ID=cassandracluster.1ee32629-c84c-11e4-b9cd-089e0150898e -e PORT_8012=8012 -e PORT=7199 -e PORT_7001=7001 -e PORTS=7199,7000,7001,9160,9042,8012 -e PORT3=9160 -e PORT1=7000 -e PORT_7000=7000 -e MARATHON_APP_ID=/cassandracluster -e PORT0=7199 -e PORT2=7001 -e MESOS_SANDBOX=/mnt/mesos/sandbox -v /tmp/mesos/slaves/20150304-161802-1420689674-5050-25118-S7/frameworks/20150304-161802-1420689674-5050-25118-0000/executors/cassandracluster.1ee32629-c84c-11e4-b9cd-089e0150898e/runs/48422628-7a85-4f8a-8d47-0833386659cc:/mnt/mesos/sandbox --net bridge -p 7199:7199/tcp -p 7000:7000/tcp -p 7001:7001/tcp -p 9160:9160/tcp -p 9042:9042/tcp -p 8012:8012/tcp --name mesos-48422628-7a85-4f8a-8d47-0833386659cc yrobla/cassandra:cluster': exit status = exited with status 1 stderr = time="2015-03-11T17:10:02-07:00" level="fatal" msg="Error response from daemon: Cannot start container 27ed6effb600e3199af38c5d10b245af2fb9e0de5d3bff40a3af08c18a2c3561:  (exit status 1)"

Well, i would look at the cassandra logs, it should give more info about
it, and the reason why the container cannot be started.
Btw, i filed new versions of the modules into my github (
www.github.com/yrobla)
2015-03-12 1:10 GMT+01:00 sonali2197<EMAIL_ADDRESS>
UPDATE: I was able to get the first node running, but when i run the
second json to connect with the SEED, it exists with the error:
Container '48422628-7a85-4f8a-8d47-0833386659cc' for executor
'cassandracluster.1ee32629-c84c-11e4-b9cd-089e0150898e' of framework
'20150304-161802-1420689674-5050-25118-0000' failed to start: Failed to
'docker run -d -c 1024 -m 536870912 -e PORT_9042=9042 -e PORT_7199=7199 -e
MARATHON_APP_VERSION=2015-03-11T23:56:05.459Z -e HOST=
svdpdac017.techlabs.accenture.com -e PORT_9160=9160 -e PORT5=8012 -e
CASSANDRA_TOKEN=1 -e CASSANDRA_SEEDS=<IP_ADDRESS> -e PORT4=9042 -e
MESOS_TASK_ID=cassandracluster.1ee32629-c84c-11e4-b9cd-089e0150898e -e
PORT_8012=8012 -e PORT=7199 -e PORT_7001=7001 -e
PORTS=7199,7000,7001,9160,9042,8012 -e PORT3=9160 -e PORT1=7000 -e
PORT_7000=7000 -e MARATHON_APP_ID=/cassandracluster -e PORT0=7199 -e
PORT2=7001 -e MESOS_SANDBOX=/mnt/mesos/sandbox -v
/tmp/mesos/slaves/20150304-161802-1420689674-5050-25118-S7/frameworks/20150304-161802-1420689674-5050-25118-0000/executors/cassandracluster.1ee32629-c84c-11e4-b9cd-089e0150898e/runs/48422628-7a85-4f8a-8d47-0833386
659cc:/m nt/mesos/sandbox --net bridge -p 7199:7199/tcp -p 7000:7000/tcp -p
7001:7001/tcp -p 9160:9160/tcp -p 9042:9042/tcp -p 8012:8012/tcp --name
mesos-48422628-7a85-4f8a-8d47-0833386659cc yrobla/cassandra:cluster': exit
status = exited with status 1 stderr = time="2015-03-11T17:10:02-07:00"
level="fatal" msg="Error response from daemon: Cannot start container
27ed6effb600e3199af38c5d10b245af2fb9e0de5d3bff40a3af08c18a2c3561: (exit
status 1)"
—
Reply to this email directly or view it on GitHub
https://github.com/yrobla/docker-cassandra/issues/1#issuecomment-78400513
.

--
Yolanda Robla
ysoft, Internet y Programación SLU
email<EMAIL_ADDRESS>teléfono: 605641639

Thanks for the response. Do i just have to update my son to pull from yrobla/docker-cassandra for both the first and second nodes?
Also, the only logs that created are the ones on the mesos-slavos which try to start the cassandra.
Will this approach allow me to scale to more nodes (4 node cassandra ring) on just two mesos-slavos?

Hi there, sorry did u manage to get the second json file?
Thanks in advance

Hi, sorry but I have not been maintaining this for a while. I see that there is a fork by christobill that looks more active, can you try that?


Updating 861 package_data for 2021 early release

Updated all the relevant 861 package data csvs for the 2021 Early Release. On the column maps, I mostly just incremented the non-sentinel column numbers by one to accommodate the early release warning column added on the left, I also checked that the number of columns were correct.

I updated the EIA-861 data archives to include the newest data from EIA including the 2021 ER. Found one typo in one of the column maps and added 2021 to the valid years for EIA-861. But something is still broken. Will have to debug tomorrow. I pushed the changes to this branch: https://github.com/catalyst-cooperative/pudl/tree/eia861_2021er


Expose types for Image

Description
Closes #1904 by exposing the types for the Image's props.
Additional context

Before submitting the PR, please make sure you do the following:

[x] Read the Contributing Guidelines
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123)
[x] Update docs in this repository according to your change
[x] Run yarn changeset add if this PR cause a version bump based on Keep a Changelog and adheres to Semantic Versioning

@davidhousedev 👀


fix: update tray icon and add on right click event for linux

fix for: #13

@mikaelkristiansson i am interested by your change for another tauri project. in your linux distribution does the main window show on left tray icon click?
For me on PopOS (ubuntu) if i do left click or right click i only see a menu with a "quit" entry.
Also did you install libayatana-appindicator3-1 on your distrib?
thanks

@mikaelkristiansson i am interested by your change for another tauri project. in your linux distribution does the main window show on left tray icon click? For me on PopOS (ubuntu) if i do left click or right click i only see a menu with a "quit" entry. Also did you install libayatana-appindicator3-1 on your distrib? thanks

I have not found a good solution yet for this. This fix only allows it to open on right click, but that is still a bit buggy and I cant test this on linux though since I dont have access to any. I read about the libayatana-appindicator3-1 but I havent tried it. If you have any success please share! 🙏


Regression in release 0.2.6

Broccoli funnel filters out files in subdirs that would have matched the include filters in earlier versions.
    var tree = new Funnel(iconsPath, {
      include: [ '*.scss' ],
    });

  readdirSync(iconsPath); // returns ['icons.scss', ...]

A glob of *.scss generally should not include subdirectories (it should only match .scss files in the root of the tree), nested subdirectories would be matched by **/*.scss.
If it previously did match I guess it is a breaking change, but making *.scss match all subdir contents is somewhat weird.

the example and the description appear different. the example does not include sub-dirs for the matcher.

Can you give us an example contents of the input tree, and which specific files you expected to be matched by include: [ '*.scss' ]?

Anyways, I believe I have solved the issue. Or maybe just one that manifests in a similar way

doing a NOM, should fix. Be sure your local copy of walk-sync-matcher is 0.2.2 or greater.


call BeginPlay() only once with AuthorityChanged, part 1 for draft re…

Contributions: We are not currently taking public contributions - see our contributions policy. However, we are accepting issues and we do want your feedback.

Description
First attempt at calling BeginPlay() only once with authority.  Testing and other work (generally the stuff noted with CMS_TODO in this PR) is underway.  This PR is only for draft feedback.  Let me know if you have thoughts on any of the CMS_TODOs also.  Thanks!
This new approach adds Pre and Post begin play delegates into the Actor class.  The GSM registers methods on these delegates and can therefore set authority as desired for each actor.
For reference, the engine diff in Actor.cpp, in DispatchBeginPlay():
	// BEGIN_IMPROBABLE
	bool bOutSwappedRoles = false;
	PreBeginPlayDelegate.ExecuteIfBound(this, bOutSwappedRoles);
	// END_IMPROBABLE
	BeginPlay();
	// BEGIN_IMPROBABLE
	const bool bWasSwappedInPreBeginPlayDelegate = bOutSwappedRoles;
	PostBeginPlayDelegate.ExecuteIfBound(this, bWasSwappedInPreBeginPlayDelegate);
	// END_IMPROBABLE

Tests
In both local and test deploys, startup actors and dynamic actors behave as expected (only calling BeginPlay() with authority once) during the following test sequences:
test sequence 1

Start deployment with small test level containing startup actors and dynamic actors
Allow everything to load on Auth Worker 0, view inspector and raw log debug output
Kill Auth Worker 0 via inspector
Allow everything to load on Auth Worker 1, view inspector and raw log debug output

test sequence 2

Start deployment with small test level containing startup actors and dynamic actors
Take snapshot of deployment
Reload deployment from snapshot

Initial tests of Singletons also seem to work so far.
Sublevel actors introduce additional complexities that i'd like to address as part of the 2nd pass (after we have everything working for startup actors).
Primary reviewers
Requesting feedback from Michael and Sahil specifically, but anyone else feel free to chime in.

Was there an engine PR to go with this @cmsmithio ?

Yes, I have the changes in a branch off improbableio/UnrealEngine, branch
feature/UNR-1486-beginplay-once-auth-server.  I think there are permission
issues preventing the creation of the PR right now, and i've filed a ticket.
You can view the commit directly here:
https://github.com/improbableio/UnrealEngine/commit/e47b4b5af804951b773a8a447f09ed6e68ea9f25
Chris
On Fri, 21 Jun 2019 at 05:07, Michael Samiec<EMAIL_ADDRESS>wrote:

Was there an engine PR to go with this @cmsmithio
https://github.com/cmsmithio ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spatialos/UnrealGDK/pull/1023?email_source=notifications&email_token=AKP56567OPCJ6GFX4S2ALX3P3SY67A5CNFSM4HXRFUS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYIFP6Q#issuecomment-504387578,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKP5654AG7APCCMR267LJZ3P3SY67ANCNFSM4HXRFUSQ
.

Going with a new approach

I've shared an item with you:
2019-08-26 State of Snapshot Reloading
https://docs.google.com/document/d/17tLzyaVy2FMl8rbZDCkJ0k7vbJBhvesPj0oKY8Gtgo0/edit?usp=sharing&invite=CJfpwN8F&ts=5d643775
It's not an attachment – it's stored online. To open this item, just click
the link above.


Add Jaeger CSV and Package for OLM integration and deployment of the …

…operator through OperatorHub

This pull requests introduces a CSV and Package which can be bundled together and used by the Operator Lifecycle Manager to install, manage, and upgrade the Jaeger Operator in a cluster.

The Jaeger operator versions available to all Kubernetes clusters using OLM can be updated by submitting a pull request to the Community Operators GitHub repo that includes the latest CSVs, CRDs, and Packages.

The CSV was created based of the documentation provided by OLM and the documentation provided by OperatorHub.

The operator and the CSV were tested using the scorecard functionality recently introduced to the Operator-sdk. Currently, the Jaeger operator scores a 4/18 on the scorecard tests.

OLM integration could be improved by future code changes to the Operator:

Addressing the operator-sdk scorecard tests that failed.
Adding additional information to the Jaeger CSV based on the CSV documentation provided by OLM
Adding additional information to the Jaeger CSV based on the CSV documentation provided by OperatorHub

LGTM


Simplify Cypher queries

BI Q6 could be formulated as:
MATCH (tag:Tag {name: $tag})<-[:HAS_TAG]-(message:Message)-[:HAS_CREATOR]->(person:Person)
OPTIONAL MATCH (message)<-[likes:LIKES]-(:Person)
WITH person, message, count(likes) AS likeCount
OPTIONAL MATCH (message)<-[:REPLY_OF]-(reply:Comment)
WITH person, message, likeCount, count(reply) AS replyCount
WITH person, count(message) AS messageCount, sum(likeCount) AS likeCount, sum(replyCount) AS replyCount
RETURN
  person.id,
  replyCount,
  likeCount,
  messageCount,
  1*messageCount + 2*replyCount + 10*likeCount AS score
ORDER BY
  score DESC,
  person.id ASC
LIMIT 100

BI Q7 is currently quite inefficient as it can compute the popularityScore of a certain Person multiple times.

https://github.com/ldbc/ldbc_snb_implementations/blob/dev/cypher/queries/bi-5.cypher


[metrics-advisor] Migrate @azure/ai-metrics-advisor to ESM/vitest

Packages impacted by this PR

@azure/ai-metrics-advisor

Issues associated with this PR

https://github.com/Azure/azure-sdk-for-js/issues/31338

Describe the problem that is addressed by this PR
Migrates the @azure/ai-metrics-advisor package to ESM/vitest via automation.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.


MAISTRA-1627: Fix lint and gen-check failures

/retest

/retest

/retest

Fixed the Copyright

/test lint

/test unit

/test integration

All tests pass now. Turns out integration tests had an issue. Created MAISTRA-1660 for that.
Pulled in the fix for it from upstream 1.6 branch in this PR so that all tests pass and we have a single PR fixing all test/lint failures.

@jwendell This PR seems to include more than just lint and gen-check failures, can these be separated out into individual PRs?

no. If we split it, tests will fail for both PR's. Unless we force-merge them.

@jwendell  please create a second JIRA to cover the additional work and include it in the description of this PR, we should not be sneaking in additional changes just for expedience.

@knrc done


Separate out list of well-known counters into its own doc

Summary
This PR separates the list of well-known counters to its own reference doc. We also need to do some more work to ensure the new counters added in the BCL is documented, so I will be following up with another PR for that.
I also fixed some counter descriptions and added a link to the EventCounter docs from the main diagnostics landing page.
Part of https://github.com/dotnet/diagnostics/issues/515

Please check for a clean build before merging.


How to override the default sql Insert,Update methods?

Hi,
Is it possible to customize the sql insert and update methods for some of the models?
I want to add "AddDate", "UpdateDate" which will store the adding and updating date of the record.
Thanks in advance.

I got is, Thanks


Explore Playdown

Playdown is a tool that can convert a Swift file to Markdown. This might be really helpful for generating documentation, since we can verify that the Swift code within the documentation builds and runs successfully.

Let's tackle this when we create a separate repository for examples. We can migrate the current readme to a playground file with markdown comments. The playground helps us ensure that the code is up-to-date and builds correctly. Then we can make updates to the playground and run Playdown to convert it to markdown for the readme.

We've settled on Jazzy as our documentation generation tool.


Refactor etl/init.py to make adding new modules easier.

Overview
This changes how we add new modules to the ETL so we only have to add them in one place. Also it organizes them slightly.
Finally, there's a tiny opportunistic change to the docs to remove a reference to dev.
Testing
How did you make sure this worked? How can a reviewer verify this?

Checked to see that all modules on the left do indeed show up on the right.
Loaded up Dagster UI and saw that the ETL appears to still be there

# To-do list
- [x] Ensure docs build, unit & integration tests, and test coverage pass locally with `make pytest-coverage` (otherwise the merge queue may reject your PR)
- [x] Review the PR yourself and call out any questions or issues you have

The main duplication that's being removed here is that we're now using the same dictionary of modules to load assets and also to load asset checks, right?  This definitely tripped me up for a bit when I was trying to add an asset check to the GridPath RA Toolkit data.

The main duplication that's being removed here is that we're now using the same dictionary of modules to load assets and also to load asset checks, right? This definitely tripped me up for a bit when I was trying to add an asset check to the GridPath RA Toolkit data.

Yep, exactly!


Improve VSOCK communication security by introducing built-in TLS connection blocks

What this PR does / why we need it:
Without additional validation, it is not possible for an agent in the guest to find out if a connection attempt comes from virt-handler, another privileged service, or from an unprivileged random user. This stems from the fact that while listening on ports <=1024 requires CAP_NET_BIND_SERVICE, connecting to port <=1024 does not require any privileges.
We pushed for example to containerd a change that any containerized workload can not do these types of connections without privileges, but a random logged in user to a node could still connect.
If an agent now provides an interface which allows for instance injecting public ssh keys, any random user could inject their keys into all VMs if they gain access to a node.
To prevent this  type of attack, the following improvments are introduced:

A virt-handler system grpc service is exposed by virt-handler on port 1.
This type of service requires CAP_NET_BIND_SERVICE, so arbitrary users can not provide this service
This system services exposes a CA method which allows clients to fetch the current kubevirt CA bundle
A tls parameter is added to the vsock-websocket  all to request a TLS encrypted connection over vsock
TLS encryption over virt-handler will be the default. If a custom encryption layer is going to be used the parameter can be set to false.
virt-handler will at least right now not attempt a server-certificate validation.

A vsock client can now:

expose a service on a port <=1024
fetch the current CA bundle from the system service on every connection attempt
and verify the certificate against that CA bundle

Given that both, client and server were as part of this authentication flow listening on a port <=1024 there is a pretty good guarantee that two services with CAP_NET_BIND_SERVICE (one from the node view, the other one from the guest OS view) are talking to each other. This makes it hard for arbitrary users to take such session over.
Finally an example guest agent is included, to demonstrate on how to implement this type of flow.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

Add basic TLS encryption support for vsock websocket connections

/cc @rthallisey
/cc @zhuchenwang

@zhuchenwang FYI, would be great if you could have a look.

/retest

@rthallisey happy if you can have another look.

Change lgtm.  Will add the label after a rebase.

/lgtm

/retest

/test  pull-kubevirt-e2e-k8s-1.24-sig-compute
unrelated flake

/check-dco
/approve

/retest

/test pull-kubevirt-e2e-k8s-1.24-sig-compute-root
failed on an unrelated flake.


robots.txt is not valid

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed.
👣 Steps to reproduce
Run "lighthouse" in Chrome
🔬 Expected behavior
robots.txt should validate
🌳 Environments
All

I don't understand why QIT gets this error, as far as I can tell there is not a robots.txt file.  If I add one in my local dev env, I still get the malformed error.
I found this link which seemed promising but it also did not work. :man_shrugging:
https://medium.com/@andrewzey/google-seo-with-create-react-app-fixing-the-hidden-gotcha-c164063106d


ARROW-7066: [Python] Allow returning ChunkedArray in arrow_array

This PR needs rebasing for the CI changes.

Rebased this, and all green except waiting on Appveyor


v1.0.1 release

I think the base branch should be main instead of development.

I posed 2 questions, but other than those everything looks good.
The version number increments the micro revision rather than the minor revision, but after a discussion with David that seems purposeful (in which case I'll create the v1.1.0 release when the endaq.plot officially goes to 1.1.0)

Apologies for the false start. Another PR has been created (#46) with the correct branch names and versions.


chore: configure pnpm workspaces

This PR uses pnpm workspaces to configure the monorepo.
The main pnpm file is pnpm-workspace.yaml in the top-level directory.
This file tells pnpm which folders in the monorepo are TypeScript/JavaScript packages.
Running pnpm install automatically builds all those packages.
The pnpm workspaces also simplify inter-package dependencies.
For example, example apps have dependencies to the typescript client and the generator, which can be defined as follows in their package.json:
"dependencies": {
  "electric-sql": "workspace:*",
},
"devDependencies": {
  "prisma-generator-electric": "workspace:*"
}

Thus, for every package in the monorepo, we modified the inter-package dependencies accordingly.
The rest of this PR consists of modifying the GitHub workflows such that CI uses pnpm.

@alco,

@kevin-dp There still remain scripts that invoke yarn, namely:
* `e2e/migrations/sattelite.luxinc`

* `e2e/satellite_client/Makefile`

* `e2e/satellite_client/package.json`

And a few uses of npm:
* `.github/workflows/clients_typescript_publish.yml`

* `clients/typescript/package.json`

* `e2e/satellite_client/package.json`

Don't those need to be updated to use pnpm instead?

Going through them:

e2e/migrations/satellite.luxinc:
e2e/migrations directory is deprecated and should have been removed probably, only single_dc, multi_dc and migrations_v2 are enabled, as signified by the LUX_DIRS variable in e2e/Makefile
e2e/satellite_client/Makefile:
That one is correct, although I'm not sure if node_modules or local-build targets are actually used. I've pushed a commit which makes the targets correct and removes yarn
e2e/satellite_client/package.json:
Also correct, I've replaced yarn with npm

For npm mentions, they are OK, since we only use npm run or npx (and npm config set which works properly with release-it tool). We only care that npm is not used for script installation, it will correctly use packages installed by pnpm.

@icehaunter thanks for clarifying!


🐸 Add NVIDIA CUDA

This pull request:

Resolves https://github.com/ministryofjustice/analytical-platform/issues/4418
Adds NVIDIA CUDA
Adds but comments out some variables relating to NVIDIA (source)

Notes:

Release ubuntu2404-cuda-rc1 fails with:nvidia-container-cli: requirement error: unsatisfied condition: cuda>=12.5, please update your driver to a newer version, or use an earlier cuda container: unknown

SMI output https://mojdt.slack.com/archives/C04M8224WCV/p1715171685297119?thread_ts=1715170069.619749&cid=C04M8224WCV

TODO:

[ ] Delete release ubuntu2404-cuda-rc1

Signed-off-by: Jacob Woffenden<EMAIL_ADDRESS>

🤝


Systemd-enabled distro fails to boot with unhelpful error message if systemd is not installed

Version
<IP_ADDRESS>
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>-microsoft-standard-WSL2
Distro Version
Custom Fedora
Other Software
No response
Repro Steps
Enable systemd via wsl.conf in a distro that does not have systemd installed.
Expected Behavior
Launch fails, with an error message indicating why it didn't work (e.g. something about systemd being unavailable).
Actual Behavior
Terminal message says Catastrophic Failure with error code Wsl/Service/0x8000ffff.
Diagnostic Logs
No response

Fair - could / should probably do a quick check if the binary actually exists. I'll make that change.

FYI for others that put their distro into a bad state by doing this, you can edit your /etc/wsl.conf file by:
%userprofile%\.wslconfig
[wsl2]
safeMode=true

Got the same issue with custom Fedora 36 after addendum to /etc/wsl.conf with:
[boot]
systemd=true

@bricss Try safeMode as above, then sudo dnf install systemd -y. Shutdown WSL after with wsl --shutdown, unset safe mode, then try again.

@reynoldsa thank you! works like a charm ✨

@reynoldsa thank you! works like a charm ✨

Also Btw Why this error happens like when i turn on systemd by editing /etc/wsl.conf
when upgrading ubuntu
error :
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
libnss-systemd : Depends: systemd (= 249.11-0ubuntu3.6) but 245.4-4ubuntu3.18 is installed
libpam-systemd : Depends: systemd (= 249.11-0ubuntu3.6) but 245.4-4ubuntu3.18 is installed
systemd : Depends: libsystemd0 (= 245.4-4ubuntu3.18) but 249.11-0ubuntu3.6 is installed
systemd-sysv : Depends: systemd (= 249.11-0ubuntu3.6) but 245.4-4ubuntu3.18 is installed
systemd-timesyncd : Depends: systemd (= 249.11-0ubuntu3.6) but 245.4-4ubuntu3.18 is installed
udev : Breaks: systemd (< 249.11-0ubuntu3.6) but 245.4-4ubuntu3.18 is installed
Recommends: systemd-hwe-hwdb but it is not installed

WSL --version
WSL version <IP_ADDRESS>.0

I did the same as @bricss but can't enable safe mode on Windows11 WSLg version 1. I enabled the debug console in .wslconfig and that works. The kernel is doing something before it fails, but I'm unable to get a shell such that I can disable or install systemd.

WSL --version
WSL version <IP_ADDRESS>.0

I did the same as @bricss but can't enable safe mode on Windows11 WSLg version 1. I enabled the debug console in .wslconfig and that works. The kernel is doing something before it fails, but I'm unable to get a shell such that I can disable or install systemd.

Same issue here
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.47
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.900
Using fedora in wsl.
Adding safe mode doesn't work , however I can go into default ubuntu distro

@somu1795 you can work around it by converting it to the old WSL version, not to be confused with WSL release version, if that makes sense.
wsl --set-version <Distro> 1

It took me a few minutes before it was done, but after that it was able to run. I could then delete the wsl.conf file and convert it back to WSL 2.

@paller Thank you for the workaround, it's working on my case [openSUSE-Leap-15.4]

Mounting the vhdx image file on another distro made possible to edit the /etc/wsl.conf on faulty system.
On Windows:
wsl -d <working system> --mount --vhd <path to image>\<image name>.vhdx --bare
Example: wsl -d Ubuntu-20.04 --mount --vhd c:\wsl\vms\Ubuntu-22.04\Ubuntu-22.04.vhdx --bare
Inside the working system:
Mount the device on a mount point (Example: sudo mount /dev/sdd /mnt)
Edit the <mount point>/etc/wsl.conf, removing the [boot] systemd=true part.
Umount and exit the system.
Back on Windows, umount the image:
wsl --unmount \\?\<path to image>\<image name>.vhdx
Example: wsl --unmount \?\c:\wsl\vms\Ubuntu-22.04\Ubuntu-22.04.vhdx
Check if the former faulty system boot up.

I knew it was a good idea to add a "make sure systemd is installed" step to the documentation.
Unfortunately, since I've only installed one distro under WSL and it was so long ago that I don't remember if I uninstalled systemd myself or if it started out like that, I wasn't sure what to say about whether it's likely to be preinstalled etc. and so didn't feel qualified to add that step to the documentation myself.
And I definitely hadn't thought about the fact that it would be difficult to fix things if you tried to boot a distro with systemd enabled but not installed, so I wouldn't have added a "warning" block or whatever to call out the danger even if I had written this up and it had gotten merged. Oh well.


Rendering issue - ImportError

Hey Kevin,
In DiscreteCarFlag-v0 env for gym==0.18.0, running it with the --render flag returns the traceback:
Loading using gym.make
Traceback (most recent call last):
  File "run.py", line 333, in <module>
    run_experiment(parser.parse_args())
  File "run.py", line 21, in run_experiment
    env = env_processing.make_env(args.env)
  File "/home/hp/Desktop/ashok/DTQN-paper/utils/env_processing.py", line 46, in make_env
    env = gym.make(id_or_path)
  File "/home/hp/miniconda3/envs/dtqn/lib/python3.8/site-packages/gym/envs/registration.py", line 145, in make
    return registry.make(id, **kwargs)
  File "/home/hp/miniconda3/envs/dtqn/lib/python3.8/site-packages/gym/envs/registration.py", line 90, in make
    env = spec.make(**kwargs)
  File "/home/hp/miniconda3/envs/dtqn/lib/python3.8/site-packages/gym/envs/registration.py", line 59, in make
    cls = load(self.entry_point)
  File "/home/hp/miniconda3/envs/dtqn/lib/python3.8/site-packages/gym/envs/registration.py", line 18, in load
    mod = importlib.import_module(mod_name)
  File "/home/hp/miniconda3/envs/dtqn/lib/python3.8/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 843, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/hp/Desktop/ashok/DTQN-paper/envs/car_flag.py", line 12, in <module>
    from gym.utils import pyglet_rendering as visualize
ImportError: cannot import name 'pyglet_rendering' from 'gym.utils' (/home/hp/miniconda3/envs/dtqn/lib/python3.8/site-packages/gym/utils/__init__.py)

The solution is to replace
from gym.utils import pyglet_rendering as visualize

with:
from gym.envs.classic_control import rendering as visualize

Hi Ashok, thank you for pointing this out! I have updated the paper and main branches with your fix :+1: