Feature Request - multiple webhooks

The ability to have webhook1, webhook2, webhook3 etc, & then be able to choose which webhook(s) the messages are sent to

Multiple webhooks gets really complicated if you want to be able to customize all of them. Not sure how to really tackle this.
Might have to abstract the message sending to a webhook controller which can set up a message for each webhook as needed for every event

yeah... I was hoping it'd be easy to add something like
Webhooks = https://URL.one;https://URL.two
but I don't know how any of that is handled with this. I really should read through the source code more to get a better understanding, even if I don't know cs
I do have some ideas on simplifying the configs in general though... I might send you a copy later to see what you think

Multiple webhooks can work this way:
Webhook1Url=https://...
Webhook2Url=https://...
Webhook3Url=https://...

ContentForWebhook1=ServerStart,ServerStop,Join,Leave,Death,Ping,Shout
ContentForWebhook2=ServerStart,ServerStop,GameSaved
ContentForWebhook3=All

Then it can be determined what to send where when dispatching the content to discord.

2 webhooks are supported with 2.1.9 in PR #170


Verified Layer lags behind

When layer j+1 starts we start "processing" layer j, by running the Tortoise on it (then update state etc., if pbase advances). Therefore, when our last synced layer is k, our VerifiedLayer is k-1.
There are 2 issues:

The App shows a difference of 3, instead of 1 (k and k-3)
There is a new change in the code where it seems that the miner processes layers with a delay of one layer.

For point 2, the following screenshots are from the running testnet, where we compare old miners to a new one (with the new code):

Layer hash is computed one layer late (5 minutes after the rest)

New state root is also computed one layer late, also there are 2 logs of "new state root" for some reason

Looking at the code in grpc_server.go, we see that in fact the "verified layer" is "latest layer in state" (VerifiedLayer: s.Tx.LatestLayerInState().Uint64()) which means that point 1 above is fine: we are verifying k-1, p_base is k-2, and the latest layer in state is indeed k-3.
Point 2 above should still be addressed.

@barakshani  Does this issue cover the case we see where the verified layer lags 10-15 layers behind the tip? If not - we need another issue for this observed bug that we see in some f&f clients.

No, but as far as I know a fix for what you are talking about is part of this PR https://github.com/spacemeshos/go-spacemesh/pull/1785. I don't know if the solution is tested. It is not merged into closed_tn yet.


24h graph span with 1d group by lists multiple days along X-Axis

Checklist

[x] I updated the card to the latest version available
[x] I cleared the cache of my browser
[x] I verified that I'm really running the lastest version in my browser console
[x] I checked if there is another issue opened with the same problem

Describe the bug
With the below configuration I believe it should only have the current date with two bars that auto-fill the width, but instead the x-axis shows multiple days in the future and the bars are not even under the correct date (today is 7/8 and they display under 7/10).
The X-Axis has 7/9 - 7/12 displayed.
Code:
type: custom:apexcharts-card
update_interval: 15m
graph_span: 24h
span:
  start: day
apex_config:
  yaxis:
    show: true
    decimalsInFloat: 0
    tickAmount: 12
    min: 0
    max: 24
series:
  - color: purple
    entity: sensor.office_lights
    name: Office
    type: column
    group_by:
      func: max
      duration: 1d
  - color: green
    entity: sensor.lr_lights
    name: living room
    type: column
    group_by:
      func: max
      duration: 1d

configuration.yaml
sensor:
  - platform: history_stats
    name: LR_Lights
    entity_id: light.living_room_recessed_lights
    state: "on"
    type: time
    start: "{{ now().replace(hour=0, minute=0, second=0) }}"
    end: "{{ now() }}"

  - platform: history_stats
    name: Office_Lights
    entity_id: light.office_recessed_lights
    state: "on"
    type: time
    start: "{{ now().replace(hour=0, minute=0, second=0) }}"
    end: "{{ now() }}"

Version of the card
Version: 1.9.0
Screenshots

Expected behavior
I'm trying to have the total time on per day per entity refreshed every 15 minutes.
The X-Axis should be labeled with only the current date and contain a bar for each entity I add.  Since it's grouped by the single date (midnight - 23:59), this particular example should have two large bars that fill the width of the card.
Desktop (please complete the following information):

Browser Safari
Version: MacOS Big Sur

Following up with this issue - any help would be appreciated...


Fix #368: fix for highlight open file on launch

@flukeout
@humphd
@gideonthomas
Hey,
Managed to hopefully fix this problem.

Let me know if you have any suggestions or addition, I'm still working on getting the white font.:)

Fixes mozilla/thimble.mozilla.org#368

Awesome, great job.  Related work happening in #587

Hi @Th30 - Unfortunately I don't think this addresses the issue. The change you've made forces the DIV that shows a file highlight to be shown with the display: block !important rule. That DIV is always there at the top location until it's shown by Brackets when a file is selected.
So, if you edit a file that is in the second location, the reload brackets, the second file will be in the Editor, but the highlight will always be shown in the first position.

Ah ok I'll retest and see what I need to change, I might need to check the Javascript as well, for the dynamically created files.

I'll close this PR then @Th30 - happy to follow up in new PRs or other issues you want to try!


YAML error: line 3: mapping values are not allowed in this context

I used theme watch as normal, but for some reason I receive the following error:
13:26:45 YAML error: line 3: mapping values are not allowed in this context
My config.yml:
development:
  password: 6317987e924c1c255974eee9424011e5
  theme_id: "31926845541"
  store: smallpetselect.myshopify.com
  directory: shop
  ignore_files:
    - config/settings_data.json

deploybot_dev:
  password: 6317987e924c1c255974eee9424011e5
  theme_id: "2391212058"
  store: smallpetselect.myshopify.com
  directory: shop
  ignore_files:
    - config/settings_data.json

live:
  password: 6317987e924c1c255974eee9424011e5
  theme_id: "2404876314"
  store: smallpetselect.myshopify.com
  directory: shop
  ignore_files:
    - config/settings_data.json
  readonly: true

Strangely, I checked out a different branch with a different version of config.yml, where theme watch worked as long as I was on the branch. But if I copy and paste the contents of the working config.yml exactly onto my current branch, theme watch fails with the same error as above.
The working config.yml is:
development:
  password: 6317987e924c1c255974eee9424011e5
  theme_id: "31876153445"
  store: smallpetselect.myshopify.com
  directory: shop
  ignore_files:
    - config/settings_data.json

live:
  password: 6317987e924c1c255974eee9424011e5
  theme_id: "2404876314"
  store: smallpetselect.myshopify.com
  directory: shop
  ignore_files:
    - config/settings_data.json
  readonly: true

I validated the YAML and it looks fine. What could be wrong?
OS (including version): MacOS Sierra 10.12.6 (16G1212)
Themekit version: 0.7.5
Ignore Files(if any):
# Windows image file caches
Thumbs.db
ehthumbs.db

# Folder config file
Desktop.ini

# Recycle Bin used on file shares
$RECYCLE.BIN/

# Windows Installer files
*.cab
*.msi
*.msm
*.msp

# Windows shortcuts
*.lnk

# =========================
# Operating System Files
# =========================

# OSX
# =========================

.DS_Store
.AppleDouble
.LSOverride

# Thumbnails
._*

# Files that might appear in the root of a volume
.DocumentRevisions-V100
.fseventsd
.Spotlight-V100
.TemporaryItems
.Trashes
.VolumeIcon.icns

# Directories potentially created on remote AFP share
.AppleDB
.AppleDesktop
Network Trash Folder
Temporary Items
.apdisk

/node_modules
/shop/config/settings_data.json
/bower_components
theme.lock

Deleting the theme.lock solved this problem.
This is usually my go-to fix for themekit  related issues, but for some reason Atom wasn't picking up theme.lock even though it was in my project. Could be time to switch back to Sublime.

This will no longer be a problem in v0.8.0 (released today) since the asset manifest has been removed from themekit.


Webhook support for API 2018-01-23

I was running into some problems on API 2018-01-23 with the differences between mocked and real webhooks, so I went through and copied all the example requests.

Closing until I handle tests.


FIX: Purge all ERB stuff

Purge:

Anywhere that mentions ERB (electron-react-boilerplate)

Closing... (since we don't use erb anymore)


Warning: No config object or "package.json" was found

Hi there, first off great project! Love it.
Secondly, no matter what I do, whether I manually configure a Gruntfile task or not, I get the following:
› grunt verb -v
Initializing
Command-line options: --verbose

Reading "Gruntfile.js" Gruntfile...OK

Registering Gruntfile tasks.
Reading package.json...OK
Parsing package.json...OK
Initializing config...OK
Loading "Gruntfile.js" tasks...OK
+ build, build_js, build_less, default, docs, lint

Running tasks: verb

Loading "grunt-verb" plugin

Registering "/srv/nerdwallet/wp/node_modules/grunt-verb/tasks" tasks.
Loading "verb.js" tasks...OK
+ verb

Running "verb" task

Running "verb:data" (verb) task
Verifying property verb.data exists in config...OK
Files: package.json -> data
Options: sep="\n", ext=".md", data=["docs/*.{json,yml}"], prefixBase, cwd="/srv/nerdwallet/wp", destBase="/srv/nerdwallet/wp", docs="docs"
Reading package.json...OK
Warning: No config object or "package.json" was found Use --force to continue.

Does the project have a package.json?

Yes it does. Are we there any specific requirements for its contents?
On Sat, Mar 4, 2017 at 11:46 AM Jon Schlinkert<EMAIL_ADDRESS>wrote:

Does the project have a package.json?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/verbose/grunt-verb/issues/12#issuecomment-284176051,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADCrriwEYRIuKNdY71N_qwUCM3Q0edPxks5rib9_gaJpZM4MTDJY
.

Honestly, I don't remember lol, this runs on a really old version of verb. I'm planning on updating this to use the latest verb as soon as we merge the dev branch. I'm not sure if I'll have time to debug this, but I'll report back if I do.

Gotcha, and what's the reason to use grunt-verb vs grunt-assemble? I've
been following the rabbit hole down starting with grunt-readme (which was
great btw!), and I'm honestly having some trouble understanding the
different use cases for one vs the other. In the case of just wanting a
better readme (TOC, split out files, etc), which tool do you most strongly
recommend?
On Sat, Mar 4, 2017 at 2:45 PM, Jon Schlinkert<EMAIL_ADDRESS>wrote:

Honestly, I don't remember lol, this runs on a really old version of verb.
I'm planning on updating this to use the latest verb as soon as we merge
the dev branch. I'm not sure if I'll have time to debug this, but I'll
report back if I do.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/verbose/grunt-verb/issues/12#issuecomment-284190309,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADCrrhWsWL2Rn0VfS7KQxpP2VKlUaiHBks5riemdgaJpZM4MTDJY
.

Also, just to confirm - am I understanding correctly that this project is
basically in a broken state right now?
On Sat, Mar 4, 2017 at 3:02 PM, Mickey Kay<EMAIL_ADDRESS>wrote:

Gotcha, and what's the reason to use grunt-verb vs grunt-assemble? I've
been following the rabbit hole down starting with grunt-readme (which was
great btw!), and I'm honestly having some trouble understanding the
different use cases for one vs the other. In the case of just wanting a
better readme (TOC, split out files, etc), which tool do you most strongly
recommend?
On Sat, Mar 4, 2017 at 2:45 PM, Jon Schlinkert<EMAIL_ADDRESS>wrote:

Honestly, I don't remember lol, this runs on a really old version of
verb. I'm planning on updating this to use the latest verb as soon as we
merge the dev branch. I'm not sure if I'll have time to debug this, but
I'll report back if I do.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/verbose/grunt-verb/issues/12#issuecomment-284190309,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADCrrhWsWL2Rn0VfS7KQxpP2VKlUaiHBks5riemdgaJpZM4MTDJY
.

UPDATE: so I think I just got to the bottom of the error in question - check this out:
{ TypeError: Path must be a string. Received [ '/srv/nerdwallet/wp/package.json' ]
  at assertPath (path.js:7:11)
  at Object.extname (path.js:1433:5)
  at Function.plasma.normalizeObject (/srv/nerdwallet/wp/node_modules/plasma/index.js:416:16)
  at Function.plasma.normalize (/srv/nerdwallet/wp/node_modules/plasma/index.js:460:31)
  at Function.plasma.normalizeString (/srv/nerdwallet/wp/node_modules/plasma/index.js:177:17)
  at Function.plasma.normalize (/srv/nerdwallet/wp/node_modules/plasma/index.js:456:31)
  at Function.plasma.load (/srv/nerdwallet/wp/node_modules/plasma/index.js:488:19)
  at plasma (/srv/nerdwallet/wp/node_modules/plasma/index.js:23:17)
  at Object.module.exports [as config] (/srv/nerdwallet/wp/node_modules/verb/lib/config.js:26:14)
  at Object.verb.process (/srv/nerdwallet/wp/node_modules/verb/index.js:115:35)
  at /srv/nerdwallet/wp/node_modules/grunt-verb/tasks/verb.js:52:23
  at Array.forEach (native)
  at Object.<anonymous> (/srv/nerdwallet/wp/node_modules/grunt-verb/tasks/verb.js:36:16)
  at Object.<anonymous> (/srv/nerdwallet/wp/node_modules/grunt/lib/grunt/task.js:255:15)
  at Object.thisTask.fn (/srv/nerdwallet/wp/node_modules/grunt/lib/grunt/task.js:73:16)
  at Object.fn (/srv/nerdwallet/wp/node_modules/jit-grunt/lib/jit-grunt.js:126:30)
  at Object.<anonymous> (/srv/nerdwallet/wp/node_modules/grunt/lib/util/task.js:294:30)
  at Task.runTaskFn (/srv/nerdwallet/wp/node_modules/grunt/lib/util/task.js:244:24)
  at Task.<anonymous> (/srv/nerdwallet/wp/node_modules/grunt/lib/util/task.js:293:12)
  at /srv/nerdwallet/wp/node_modules/grunt/lib/util/task.js:220:11
  at _combinedTickCallback (internal/process/next_tick.js:67:7)
  at process._tickCallback (internal/process/next_tick.js:98:9)
  at Module.runMain (module.js:577:11)
  at run (bootstrap_node.js:352:7)
  at startup (bootstrap_node.js:144:9)
  at bootstrap_node.js:467:3

  origin: '/srv/nerdwallet/wp/node_modules/verb/lib/config.js' }

Looks like plasma needs to receive a string, but grunt-verb is passing it an array :(

this project is
basically in a broken state right now?

It seems to be for you, so I'd say yes lol. This repo hasn't been updated for a couple of years. But verb and the verb plugin ecosystem are very active, and it's used on thousands of projects. I just haven't used grunt in a while. But like I said, I plan to update this soon.

I'm honestly having some trouble understanding the
different use cases for one vs the other.

No problem, I'll try to clarify.
tldr;

verb => markdown
assemble => HTML

We built both applications on top of base, which gives them a similar API and allows them to share plugins. But they are used very differently, have different default settings and plugins, and the CLIs behave differently.
I know you asked about the grunt-* tools, but I thought it would help to clarify what the parent libs are focused on. I'd be happy to provide more detail if it would help.

@MickeyKay btw it might be worth trying the dev branch of verb directly (not as a grunt plugin). Not every project has grunt, but every project should have a readme.
I can tell you how to get set up if you want, then there are just a couple of minor differences that I'd be happy to walk you through. Up to you, no worries either way on my end.

Thanks @jonschlinkert, much appreciated. I would love know how to integrate vanilla verb into our existing build flow, which is Grunt-based at this point in time. I can play around with the dev branch for sure, however I'll still need to at least integrate a basic Grunt wrapper, or somehow kick off the task elsewhere in our build process. It's interesting to me though, because when I look at the bottom of various readme's, I see things like:

and

I'm curious, has the former readme (grunt-assemble) just not been updated in that long, and would the build job currently break?
And for the latter (assemble), how is verb-generate-readme being run? Surely it's not just called  manually, right?

And for the latter (assemble)

Where is assemble? Or grunt-assemble? I don't see either one in the screens. Sorry I may have missed something

Those are respectively at the bottom of the readme's for grunt-assemble and assemble. So clearly those readme's were built using grunt-verb and verb-generate-readme.

Those are respectively at the bottom of the readme's for grunt-assemble and assemble.

Oooh, got it. Sorry, we use verb on 1k+ packages. those footers had not special significance to me. Makes sense now.
Both readme's were built by running the verb command at the command line. Verb's CLI automatically finds, loads, and registers any globally or locally installed "generators" (like verb-generate-readme), as well as any plugins, helpers or middleware that were defined by the user. Any other documentation generator could be a plugin or generator for verb.
To run the readme generator (verb-generate-readme) from the command line, you would do:
$ verb readme

This technically runs the default task on the readme generator (tasks in generators are just like tasks in grunt or gulp) .
Or, you can add a verb object to package.json, and define the tasks to run as an array on verb.tasks, and verb's CLI will automatically run those tasks when you run verb from the command line.
hope that helps.

I recently added this grunt-verb package into one of my own projects, and I was receiving this same error. For anyone else who may stumble upon this same thread hoping to find answers, I managed to get this working by merging my project's package.json data into the verb task's options.config object like so:
var pkg = grunt.file.readJSON('package.json');

grunt.initConfig({
  pkg,
  verb: {
    options: {
      config: Object.assign({}, pkg)
    },
    readme: {
      files: [{
        src: '.verb.md',
        dest: 'README.md'
      }]
    }
  }
});


Please Add Intec Education College

https://intec.edu.my/

@creineq Pull request merged. Thank you!


Remove reborrow on sq and cq

Because this method copies over the head/tail to a new queue, the original queue becomes outdated and useless, and pushing to it might result in overwriting sqes or at worst reading into uninitialized memory.

Thank you! I am planning to remove it.


Example script of DDPG seems incorrect

In example of DDPG, default number of epochs to train policy/qfunc is set to number of steps collected in the iteration. (for example in default setting 50000) However, this seems to cause too long iteration without performance improvement. Is this an intended implementation or just a bug?
https://github.com/DeepX-inc/machina/blob/caf2e51859e764876963f8a24982607c0774e3b2/example/run_ddpg.py#L143-L148
Other implementation like spinning up seems to use total number of episode for updating.
https://github.com/openai/spinningup/blob/master/spinup/algos/ddpg/ddpg.py

In original paper of DDPG (https://arxiv.org/pdf/1509.02971.pdf), Algorithm1 DDPG Algorithm insists that a number of updating networks is as same as a number of steps. They updates network per step. To keep consistency with respect to the ratio of interaction times (a number of steps) to update times, we pass step to epoch.


Remove extra instruction in ef-mvc tutorial

I used dotnet aspnet-codegenerator controller -name DepartmentsController -m ContosoUniversity.Models.Department -udl -scripts -dc ContosoUniversity.Data.SchoolContext -outDir Controllers on Ubuntu 17 and the scaffolded Edit view doesn't have this div!
Maybe older version of dotnet aspnet-codegenerator adds this div or when using VS on Windows?! I'm not sure...
Edit: I'm using SQL Server on Ubuntu and the tutorial uses LocalDB if this matters to aspnet-codegenerator!

@badersur Thank you again! I was also confused by this text.

You're welcome :)
On 6 Sep 2017 1:06 am, "Scott Addie"<EMAIL_ADDRESS>wrote:

@badersur https://github.com/badersur Thank you again! I was also
confused by this text.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aspnet/Docs/pull/4182#issuecomment-327303374, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABm7d9p4Gbh68ZQWL56jt9XtxszoupNiks5sfbfVgaJpZM4PK9CP
.


Include "useSSL=false" for MySQL jdbc properties

Without this flag, DXP starts with a lot of warnings:
Mon Nov 27 12:08:14 GMT 2017 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.

Already fixed by @balcsida in https://github.com/djavorszky/liferay/commit/b24925db1f362209bea5d9aec32f6618106202e3.
Issue was that I was using an outdated version of the library, hence this fix was not applied on production. Next deploy will contain it.


ipykernel does not support python 3.12

might need to limit python version to 3.11 to use with conda/jupyter lab

I'm not seeing this issue with VSCode

It's not an issue for VSCode, I don't think. You need to install ipykernel if you want to use a conda environment, then make the kernel accessible on Jupyter. However, if your python version is too high, you can't use ipykernel at present. That was the error. It won't affect anyone who isn't using conda envs and manually installs ipykernel.

I've confirmed this on mac now.

This issue may have been a non-issue, but Andy did find that for notebook to work more independently we want to install jupyter as a dependency for pyscan, and likely remove ipykernel (which is included in jupyter install). Testing this now.


about random_batch_noise?

Sir,
Have you haven the random_batch_noise function committed? thank you!

Yeah. It has fixed.
Any other problems?

when calling SRMDPreprocessing, I found that only 'sig=2.6' was used to generate the LR images.
Should it use uniform sample for sig for each image according the original paper?
thank you very much.

The kernel size is fixed
to 21×21. When applying on real world images, we use the
additive Gaussian noise with covariance σ = 15
Sorry, I think I could not make sure which parameter will represent this σ = 15, thank you ,sir!

when calling SRMDPreprocessing, I found that only 'sig=2.6' was used to generate the LR images.
Should it use uniform sample for sig for each image according the original paper?
thank you very much.

'sigma=2.6' refers to fixed test kernel, you could change the setting according to the paper.

The kernel size is fixed
to 21×21. When applying on real world images, we use the
additive Gaussian noise with covariance σ = 15
Sorry, I think I could not make sure which parameter will represent this σ = 15, thank you ,sir!

self.noise_high is sigma of noise

The kernel size is fixed
to 21×21. When applying on real world images, we use the
additive Gaussian noise with covariance σ = 15
Sorry, I think I could not make sure which parameter will represent this σ = 15, thank you ,sir!

self.noise_high is sigma of noise

thank you , sir

Could u please help me what exactly is ground truth kernel?
as for Super-resolution we consider ground truth image to be the actually HR image and LR image to be the downsampled version? So my doubt is what have we actually consider to be a ground truth kernel?


Look into Azure AD Connect request

I sent an inquiry to David Jewer as to whether we can include this in an existing iStore request (PECSF, Performance, Moodle) or if we will need to create a new one.


fix: get inheritable attribute from parent

when /mediabox is inherited from parent, can't get rect. the function getInheritableFieldValue(key) from QPDF dosen't know if key is inheritable.

Thank you very much for your fix, I have merged it now.


Will PageSections ever support element level waiting?

Hey @daneandersen,
I know we can do a page level waits with:
wait_until { element.visible? }
element.action

But will we ever see element level waiting so we can do the more sexy:
element.when_visible.action

I imagine there is some limitation right now which is causing PageSection elements to throw an error on this type of wait. Just wondering if that is something which we can reasonably overcome in the gem.
Best,
Justin

of course you can pass a block or action to when_visible : your_element.when_visible.click

@ducthanh , this does not work for elements inside page sections currently, you will receive an error. Page sections are different than page objects.

@tk8817 does @page.page_section.section_element.when_present.action not work for you?

@mrgklwong it did not work when doing it from inside the page section.

solved with watir and new element wait logic


Environment variables comment placing in .env.example

The .env.example files contains tabs and whitespaces to comment the file, which is obviously wrong, and caused trouble with some users.
So, in order to help reduce problems with .env, I think it's a good idea to update the .env.example to comment it the right way (a line above the env).

Fixed in v2.10.3


Infinitely indenting block-comments

If I use the extension as the formatter for svelte files any block-comment <script> or <style> gets constantly pushed except for its first line.

Demo (gif)

All I'm hitting here is save, while "format on save" is on.
This is in vscode-insiders 1.34.0
Not an issue at other places where css/js is inside tags (eg.: html, vue).

funky, I will be replacing the current formatting with prettier soon so should be resolved then

should be fixed in 0.8.0

I can confirm, it did fix the issue. Thanks and generally for the plugin too.


Fix shell portability issue detected on NetBSD

I'm fine with this pull request, but it needs to be made against the development branch rather than the master branch.  If you merge directly into the master branch then it will never trickle into the development branch.  So, close this request and make a  new pull request into the development branch.  Thanks!


Best way to emulate DX11.1 constant buffers in DX12

I'm building a hobby renderer on top of MiniEngine, along with a DX11 MiniEngine-workalike backend.  In DX11 mode I use the 11.1 constant buffer feature to create a single constant buffer for each material, with all constant data for all shader stages packed into the one cbuffer.  I'm trying to figure out the best way to emulate this in DX12/MiniEngine.
So far I've modified the GpuBuffer class, following the pattern in the HelloConstantBuffers sample to create the single constant buffer.  I then map individual CBVs onto the GPU resource and obtain CPU handles, which I can bind to the pipeline using a descriptor table with all the CBV CPU handles.  This works fine.
But what I want to try is embedding the constant buffers in the root signature directly, however I only have one GPU handle for the whole constant buffer, not the several I'd need for the per-shader sub-buffers.  I know the byte offsets to the start of the per-shader data in the main cbuffer - can I safely compute new GPU handles for the sub-buffers using those offsets?  Is there another approach I should try here?  Is there any performance advantage to using constant buffers embedded in the root signature, versus the descriptor table approach?
Thanks,
Dave Elder

Yes, you can safely compute new GPU handles by offsetting the 'ptr' field.  That's how you can get SetConstantBuffers1() behavior:  offset the pointer and bind it directly to the root parameters.
The advantage of using a root CBV is that it's fewer indirections for the shader.  The fastest approach is to have inline constants, but you will quickly run out of space in the root table if you go much over 4 inline constants.  You get about 13 words of data before additional parameters spill to a different buffer.
So inline constants have 0 indirections.  They are loaded directly in the shader registers by the GPU command processor.
Root constant buffers have 1 indirection.  A shader register is populated with the pointer, but the shader has to load (and wait for) the constants.
A descriptor table of constant buffers has 2 indirections.  A shader register is populated with the pointer to the table.  The descriptor must first be loaded followed by the constant value.
Each indirection is a measurable stall, but the GPU is good at hiding this latency by switching to other work.  However, multiple indirections can definitely have a noticeable impact.  And remember that if you overflow your root table, you add an indirection to everything that overflowed.
I believe in DX11, everything had 2 indirections, so DX12 makes it possible to optimize them away.  However, it's also possible in DX12 to end up with 3 indirections if you aren't conscious of how big root entries are, and how much you are using.
-James

Excellent, thanks for the info.  This should improve my strategy for laying out root signatures efficiently.  I don't yet have support for inline constants in my material system, but I plan to add that soon.  Emulated SetConstantBuffers1() should solve my general use case.
-- Dave Elder


docker inspect -s  not returning sizie

File: engine/reference/commandline/inspect.md
Steps to reproduce

run docker run -it ubuntu bash
In another terminal, check that there is a running container with docker ps.
Based on https://docs.docker.com/engine/reference/commandline/inspect/ I should now be able to get the: 'total file sizes if the type is container' if I run docker inspect -s a5638b6d233a.

Actual result
Running docker inspect -s a5638b6d233a does not display the size. Instead it returns the same result as if I didnt specify the -s option.
Docker version
Client:
 Version:           18.09.2
 API version:       1.39
 Go version:        go1.10.4
 Git commit:        6247962
 Built:             Tue Feb 26 23:52:23 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.09.2
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.4
  Git commit:       6247962
  Built:            Wed Feb 13 00:24:14 2019
  OS/Arch:          linux/amd64
  Experimental:     false

Thanks for sharing this issue. This particular content is maintained in an upstream repo. If the issue is still applicable, please help create an issue the repo at https://github.com/docker/cli/tree/master/docs/reference/commandline


Add support for "forever" in configuration

I would very much like to use forever to ensure my server remains running even if it crashes. I dont think it would be that hard to change up the config and cli.sh to accommodate for that.

We use pm2 which is similar to forever and restarts the app on crash


Implement GQE transition from New -> Available from within ReqMgr2MS

As documented here:
https://github.com/dmwm/WMCore/wiki/ReqMgr2-MicroService-Transferor
ReqMgr2 Transferor will also be responsible for a GQE state transition from the New to the Available state, which means the whole system will be relying on this MicroService before work can flow to the agents.
This needs to be enabled as of HG1905, in both testbed and production

We have discussed a new architecture for the MS Transferor module and this new GQE status is no longer needed. closing


Power Platform Build tool - Solution Import task is not taking inputs given in the "Deployment Settings File" for the Environment Variable Settings

Hi team,
I created a new json file to store the Environment variables and used the same in the Import task, but seems this input is not being executed and the values in the Target tables are not updated.  The import task shows Succesfull, but no specific logs for reading and updating the different values in the target system.
can you please advise what needs to be done ?

I have created a request there as well - https://powerusers.microsoft.com/t5/Power-Platform-and-Dynamics-365/Power-Platform-Build-tool-Solution-Import-task-is-not-taking/m-p/1675000#M496


Add IExchangeAPI.GetOrderBookWebSocket

Added a new IExchangeAPI method for streaming the order book.  This has been implemented for both Poloniex and Binance.  I also created a test in the ExchangeSharpConsole project.

Awesome, thanks for sharing!


Penetration Test Round 1 (after iATO)

Execution of security testing before go live

Will try with Burt Suite. Alvaro will help get a license 😄

Results of passive scanning using OWASP ZAP: here

Initial results of manual exploration using OWASP ZAP: here

Qualys SSL Lab scan found no issues: report (may not be persisted)

Created issues found from pen testing and source code review & testing in security risk register.

Will try with Burp Suite once we get a license.


Classify ad interests

Classify a facebook user's ad interests into categories, say sports, engineering, humor, developing, etc.
This issue has a lot of potential, and is currently only in ideation phase. Please discuss your vision about how / what can be done here.

For classifying ad interests , we can use collaborative filtering here (specifically item based one)  since it is basically a recommendation system. We can use scikit for finding similarities.Like if there is a user A and he/she searches or likes posts related to humor then we can create a system where he/she will receive the suggestions based on the tags on the other posts like humor can have tags like comedy , funny , fun etc..

@riya2908 I agree with you. Have you downloaded your fb data in json format and checked the ads interest files? can you chalk about briefly which and how will you be using those files? We'll then assign you the task :)

@xprilion I haven't downloaded my dataset , but we can gather the dataset of any user or find it online.I am not active on much social platforms.
However , I do have some path in my head.I'll jot down the pointers and will send them in slack today.

@riya2908 I suggest you to download your facebook data archive in json format before planning for the solution to this issue. It will help you to develop a solution in sync with the project. do ping in the slack channel for any queries or help you might need.

@xprilion yes sure.Thanks


Tracie v2

newest version of tracie.

Does the data dir need to be called data_public, or can it be renamed to simply data/?
The prediction format is very simple -- one prediction per line, corresponding to each question.
I wonder if it'd be easier if the questions had identifiers (as simple as "instance001", etc.), and the predictions were also JSONL files, with items like
{"id":"instance001", "prediction":"entailment"}
{"id":"instance002", "prediction":"entailment"}
{"id":"instance003", "prediction":"entailment"}
...

If you already have code that uses/produces this prediction format, then it's not worth considering. Just a thought1

Does the data dir need to be called data_public, or can it be renamed to simply data/?
The prediction format is very simple -- one prediction per line, corresponding to each question.
I wonder if it'd be easier if the questions had identifiers (as simple as "instance001", etc.), and the predictions were also JSONL files, with items like
{"id":"instance001", "prediction":"entailment"}
{"id":"instance002", "prediction":"entailment"}
{"id":"instance003", "prediction":"entailment"}
...

If you already have code that uses/produces this prediction format, then it's not worth considering. Just a thought1

Doesn't need to be data_public, I at some point saw that and thought it was a convention of some kind. data/ is just fine. Yeh, about the id point, that's fine, I think it makes sense (I don't mind either way).

@yakazimir More changes:

Renamed data_public to data
Removed the labels from the test file (instead of using "-")
Added ids to each of the files (like tracie-test-0000, tracie-train-iid-0000, and tracie-train-uniform-0000)
Made the prediction file be a jsonl file, instead of a one-label-per-line text file.

The result is that it's now harder to mismatch a prediction file and an answer file (you'll get errors like Prediction for id tracie-train-iid-0000 missing or Prediction count (1174) doesn't match answer count (860)).
Also, you can more reasonably compare prediction files, if you are comparing two model predictions, because you can match on the id.
Please have a look, and confirm that things are still running for you. (The scores returned by the evaluator are unchanged; but I used the dummy prediction file. If you use a real model, you should confirm you're still getting the numbers you expect.)

Looks fine to me. @Slash0BZ is this okay with you (perhaps you want to sanity check on a real output file)


Release GVL while the Python interpreter is running [Fix #45]

This may fix #45

ruby_thread_has_gvl_p is not exported in Ruby 2.2 and 2.1.


feat: add documentation about timezone feature

Description of changes
This PR adds documentation about the timeZone support feature.
Closes #119
Checklist
Before merging to main:

[ ] Tests
[ ] Manually tested in React apps
[ ] Release notes
[ ] Approved

Release notes
# Component changes

## Time Series

- Added X feature to Time Series.

## Leaderboard

- Fixed Y bug to Leaderboard.

## Counter

- Added Z feature to Counter.

# Package changes

## GraphQL

- Added X query to GraphQL package.

# App changes

## React 18 example

- Added X test to React 18 example.

## Storybook

- Added Y story for Time Series.

Thank you so much for this, @CBID2.
It turns out, we're migrating README to Storybook in this big PR in progress.
So could you wait on this one meanwhile? Thank you so much!

Thank you so much for this, @CBID2.
It turns out, we're migrating README to Storybook in this big PR in progress.
So could you wait on this one meanwhile? Thank you so much!

Sure no problem @ykdojo


calendar not displaying ranges properly

Version
4.5.0
Reproduction link
https://codesandbox.io/s/wizardly-pascal-jcom3
Steps to reproduce
see link
I can only reproduce it with UK timezone set
What is expected?
A contiguous calendar.
What is actually happening?
Days jumbled all over.

Added images since the bug seem to depend on what timezone you are in which may not be obvious.

Reproduced with UK timezone.

Any updates on this?

Fixed in #12172


Update to spring boot 2.1.0.RELEASE

Simple changes to allow solace-java-spring-boot to be used with spring boot 2.1.0.  I do not use this in a cloud environment and this time, so I was not able to verify that cloud functionality is not broken.

Fixes #13

Thank you for your contribution. The project has been upgrades to use the latest spring boot release.


English lessons review

Fix some typos
Remove trailing whitespace in some files
Improve the documentation lesson

Thanks for helping with the improvement the documentation lesson @milmazz! :+1:

This is fantastic @milmazz, thank you.
I'm going to add you to the repo as I have done with the other contributors/translators.  I ask that major changes go through PR and at least myself or one other contributor has a chance to look at it.


Nightly clippy lints

This PR fixes warnings raised by
cargo +nightly clippy -p argmin --all-targets --features "_full_dev" -- -D warnings

around stricter unused_imports checks.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.42%. Comparing base (35e00e2) to head (bfdd49d).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #488      +/-   ##
==========================================
- Coverage   92.42%   92.42%   -0.01%
==========================================
  Files         178      178
  Lines       24314    24314
==========================================
- Hits        22472    22471       -1
- Misses       1842     1843       +1

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


Add default meas pulse

What Changes Were Made?
Default measurement pulse included, pulled from instruction schedule map. Advantage is that this pulse is calibrated frequently, whereas the hardcoded measurement pulse can quickly fall out of date.
Also fixed a minor issue in how the plots were displayed in Jupyter notebook (remove %config InlineBackend.figure_format = 'svg' # Makes the images look nice and instead only use %matplotlib inline.
How Was This Tested?
Ran through full notebook and verified plots generated correctly and with reasonable frequency, Rabi, T1, T2, etc results.

This is nice. Thanks for updating, @zachschoenfeld33!


Not able to create lots of page

Steps to Reproduce

...
...
...

Logs

Hello @dheerajv09 !
Thank you for posting.
However, without any additional information, such as the description of the problem, code to reproduce the issue and flutter doctor -v command output, your case cannot be investigated. Due to that, closing this issue.
But feel free to open a new issue and fill the information requested in the template.
Thank you.


Prevent Accidental Node Creation Check

I have currently 4 maps on 2 of the maps when I open them the check is in the box and the other 2 when I open the check is not in the box. It would be nice if when I selected the check it would stay in or out as I set it.

This not an issue as when you finish through the workflow the default is checked.


Add route and service for getting resource category popularity

@Mtutak @mchlltt first, it looks like my linter has a different idea about how spacing should go. Let me know if this is not ok and I can update. Second, the popularity service is a lot. Ideally it would get refactored but I thought it important to work before I went down that road. Third, I left in the sql files so that we can use them if necessary in the future. If you want me to remove them I can. Thanks!

@cbrenner04 sorry about the linter issues ... I don't have strong feelings one way or another but hopefully we can try to reach some kind of equilibrium so there aren't a ton of format changes in all the diffs. At any rate, I know that I frequently end up with things on a bunch of lines where I don't necessarily prefer that, and a lot of that was fixed, so 👍 The SQL files are great and much appreciated! :) And wow that popularity service is pretty spectacular. It's looking good, though~ thanks again for setting up the INSERT statements and making some seed transaction data. I'm gonna merge this, probably?


Changes to decreased horsetail movement (FYPO:0004605)

Changes to decreased horsetail movement (FYPO:0004605)
The current definition of this term is:

A cellular process phenotype in which the occurrence of horsetail movement is decreased. Horsetail movement is the oscillatory movement of the nucleus that takes place during meiotic prophase I.

Initially I thought this would be a similar case of yes/no phenotype (abolished horsetail with a certain penetrance). It's not the case, but I think some clarifications could be made.
The term makes sense for PMID:24954111, where they measured the total length travelled by the SPB during horsetail movement. This is an interesting phenotype because it can be that in a mutant that has abnormal horsetail nucleus due to detached telomeres, the SPB still travels the same distance. See Fig. B below.

Proposed change of the definition and term name
decreased distance travelled by the spindle pole body during horsetail movement
A cellular process phenotype in which the total distance travelled by the SPB during horsetail movement is decreased. Horsetail movement is the oscillatory movement of the nucleus that takes place during meiotic prophase I.
Phenotypes I believe are wrongly annotated to this term

I think for other citations would be better annotated to something else:

PMID:9572142

lot2-s17: They don't measure the extent of the movement, but they report abnormal morphology and failure in attachment of telomeres to the SPB, so we can probably move the annotation to abnormal horsetail nucleus morphology (FYPO:0002890).
taz1-uv3 (A606V aa) same

PMID:16585273

mcp5ΔC (deltaC)[Overexpression] seems to be abolished horsetail, so should be moved to abolished horsetail movement.

PMID:17632059

taz1-uv3 and double deletion: seems to be abnormal nuclear morphology during horsetail as well.

Next steps if you agree

[x] Update term name and definition
[x] Reassign the annotations listed above (I can do this)

Logical definition will have to be updated as a consequence #4173


Charset issue fix (#718)

Description
Added substringBefore(';') to exclude any parameters after the charset one. Previously, if there were any parameters after "charset", they ended up in the charsetName variable and caused an exception on Charset.forName(charsetName) function call.
Fixed #718
Type of change
Check all that apply

[x] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Refactoring (a change which changes the current internal or external interface)
[ ] This change requires a documentation update

How Has This Been Tested?
Tested by creating extension functions Body.representationOfBytesX(), Body.asStringX() and Response.toStringX() and using them in a couple of projects. The functions itself were just a copy of the corresponding functions with small changes:

For Body.representationOfBytesX() the change was the same as in the commit - added substringBefore(';')
For asStringX() and toStringX() the only change was replacement the common functions with the extension ones created by me (mentioned before).

Checklist:

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation, if necessary
[x] My changes generate no new compiler warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Inspect the bytecode viewer, including reasoning why

Nice, this looks great! Could you please do us a favor by adding tests to verify that? Thanks! 🙇

Thank you! I have added the test in 8b37959

Let's go!

This is not the way to fix it btw. The proper way, as I've said before when I wrote this hack, is to do:

fetch all parameters
find the charset parameter
default to UTF7 / ASCII

Right now you've introduced the same bug if the the order of the params is different.

@SleeplessByte please check if a740f5ec9baee3c3a59b8cdc5ecc8952b55ae9f1 can be considered as the proper way. Thank you!


[Enhancement] dedicated button to holster weapon

While it is possible to edit the game's configuration file to disable the double tap dodge function and add a dedicated button for dodging, this is not possible with the "holster weapon" function (which is only possible by either double tapping ALT or by opening the weapon wheel). This may be possible to implement through the hook.
Even if this won't be implemented, it's a good idea for a separate plugin.

I would love to see this but I imagine this, like the skipping the opening movies, would have to be done via the scripting system. Hopefully someone works out the decompilation/recompilation of the game scripts, or CDPR makes our lives easier by just releasing a REDKit for Cyberpunk

Other mods have already dealt with this. I don't know if the creator of this mod holds the same opinion, but this mod is more targeted at performance rather than quality of life features like button remapping.

Other mods have already dealt with this.

The only 'solution' I'm aware of for this is to set "count" to 1 in the input xml file, but this doesn't actually work consistently.


Why the assignment of the reference differs from the assignment of object literal?

interface Type {
    name: string;
}

let a = {name: '', age: 0};
let b: Type = a; // Ok
let c: Type = {name:'', age:0}; // Error, why?

Why the assignment of the reference differs from the assignment of object literal?
in both cases, rules assignment compatibility?

See https://stackoverflow.com/questions/45868086/generic-function-allow-arbitrary-keys/45868742#45868742


Response of getrollout

Method getrollout has different name in CLI (getrolloutestimate)

When I invoke via http I get the following:
{
    "jsonrpc": "2.0",
    "result": [
        [
            1000,
            [
                105, 181, 212, 2, 253, 172, 6, 190, 247, 160, 183, 67, 206, 140, 195, 240, 150, 8, 65, 150, 221, 247, 82, 54, 55, 39, 103, 162, 243, 74, 169, 108
            ]
        ],
        [
            1000,
            [
                16, 148, 34, 211, 221, 51, 172, 231, 52, 34, 217, 84, 177, 36, 234, 179, 9, 232, 254, 110, 47, 170, 217, 168, 123, 37, 138, 44, 119, 70, 136, 12
            ]
        ],
        [
            1000,
            [
                65, 125, 199, 219, 219, 132, 55, 27, 7, 92, 192, 150, 102, 235, 173, 210, 38, 228, 92, 244, 171, 209, 230, 39, 17, 51, 162, 0, 227, 103, 137, 254
            ]
        ],
        [
            1000,
            [
                119, 125, 249, 125, 209, 32, 254, 22, 50, 178, 38, 160, 202, 197, 95, 129, 72, 19, 193, 222, 248, 110, 180, 144, 65, 155, 45, 131, 205, 137, 157, 156
            ]
        ],
        [
            1000,
            [
                127, 93, 223, 97, 204, 26, 221, 156, 79, 28, 174, 69, 81, 254, 138, 227, 224, 35, 122, 84, 17, 72, 77, 151, 96, 79, 189, 174, 159, 229, 227, 88
            ]
        ],
        [
            1000,
            [
                100, 139, 156, 46, 198, 217, 248, 128, 252, 164, 140, 118, 49, 209, 120, 125, 198, 49, 18, 9, 247, 9, 47, 35, 237, 66, 250, 254, 217, 94, 75, 118
            ]
        ],
        [
            1000,
            [
                23, 234, 204, 254, 139, 27, 92, 235, 4, 248, 9, 128, 164, 3, 82, 148, 2, 185, 82, 91, 255, 66, 240, 89, 38, 92, 205, 180, 115, 244, 105, 194
            ]
        ],
        [
            1000,
            [
                4, 89, 67, 128, 101, 114, 113, 188, 221, 104, 91, 46, 215, 23, 74, 26, 105, 230, 14, 203, 166, 102, 121, 51, 39, 130, 223, 102, 188, 26, 205, 74
            ]
        ],
        [
            1000,
            [
                19, 172, 22, 190, 85, 250, 127, 80, 208, 26, 243, 46, 56, 229, 33, 66, 251, 207, 159, 244, 54, 65, 69, 246, 217, 170, 11, 78, 129, 137, 226, 136
            ]
        ],
        [
            1000,
            [
                19, 133, 126, 149, 84, 61, 96, 144, 72, 1, 43, 5, 160, 1, 134, 222, 72, 79, 158, 21, 29, 111, 124, 188, 178, 60, 83, 225, 152, 158, 153, 76
            ]
        ]
    ],
    "id": 1
}

Response from CLI
[
  [
    "@mytest6",
    1000
  ],
  [
    "@mytest5",
    1000
  ],
  [
    "@mytest10",
    1000
  ],
  [
    "@mytest12",
    1000
  ],
  [
    "@mytest9",
    1000
  ],
  [
    "@mytest4",
    1000
  ],
  [
    "@mytest113",
    1000
  ],
  [
    "@mytest13",
    1000
  ],
  [
    "@mytest8",
    1000
  ],
  [
    "@mytest7",
    1000
  ]
]

Proposed fix in https://github.com/spacesprotocol/spaced/pull/20

Also it would be great to have block numbers of the rollout in the response. Right now it's not clear when the rollout will occur.


disallowPaddingNewLinesInObjects is "incorrect"

right now it disallows all new lines inside an object expression. It should instead disallow 2 new lines inside of object expressions.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/8663714-disallowpaddingnewlinesinobjects-is-incorrect?utm_campaign=plugin&utm_content=tracker%2F281640&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F281640&utm_medium=issues&utm_source=github).

Does this still apply? I don't think that's what it does at the moment - currently, it's disallowing any number of newlines between the opening brace and the remaining chunk of the object literal, and also between the closing brace and the previous chunk of the object literal.

At this point only major and CST related bugs will be fixed


iOS and macOS support

Solved by #229. The integration isn't fully published but I don't think Krayon can even be responsible for that due to kotlin native library limitations.


Heroku Support

First off, great gem. Really like how quick and powerful it is. That being said, it took me about 20 hours to come up with a good deployment plan for it on Heroku. I would have switched to EC2 or Digital Ocean if I had a choice because this issue was so bad.

Heroku runs Ubuntu 10.04 which only has icu4c v42 available unless you're able to run an apt-get update which isn't possible. This makes Steve Tooke's solution unusable.
This solution uses a heroku build pack to install the correct version of icu4c into vendor and install the gem with environment variables which is cool but relies on hosting the package on s3 and maintaining said package.
The bundled version of the gem is a completely unacceptable answer as deploys take 15+ minutes.

So is there anyway to make the gem compatible with v42 of icu4c or redesign the gem in a way that deploys to Heroku are more manageable and acceptable in terms of time?

Does today’s heroku + docker announcement make this any easier?

I stopped maintaining the app using this gem so I don't actually know. Hopefully someone else with experience can chime in on this because I have another app I would like to use this gem with but won't due to the deployment issues.

I've just published a definitive guide on wiki, check here.

I'm still maintaining this Heroku buildpack:
https://github.com/donnykurnia/heroku-buildpack-ruby
I'll merge any new stable releases to kept it up-to-date.

@sobrinho's wiki article worked perfectly. The multi buildpack is going away end of the year though so you'll need to update the instructions for that change but other than that good stuff. Going to close the issue because the wiki article resolved my issue.


Add doc that explains public VS. Stable releases

@AArnott in a case like our where we have 3 components with different version for historical reason we should update version.json like
release.branchName = "release_msbuild/v{version}"
release.branchName = "release_collector/v{version}"
release.branchName = "release_console/v{version}"
and run nbgv prepare-release inside project folder, right?

@MarcoRossignoli ugh. I don't know how well that will work or if there's a better way. I've never heard of quite your situation before when using prepare-release. I suppose you could try it and see.
But if you plan to release all at the same time as a rule, personally I might try for maintaining just one branch for each release instead of 3. That might mean that prepare-release isn't useful.
On the other hand if you might release just one package for servicing, then one branch per package might make sense.

On the other hand if you might release just one package for servicing, then one branch per package might make sense.

Eh at the moment is our use case, because the "core" is shared between 3 "drivers" but not all support all code feature(passing parameters) and "drivers" doesn't provide same "added features", but this is a "design" issue to me, maybe in future we will be able to "merge features" in core and let "drivers" to be only "pluggable entry points".
I agree...if we'll decide to "align" version some day maybe will be better.
BTW I did some tests on my custom repo, tool and the idea works very well.


Implement GitHub PR Issue Checker Workflow

Closes #156
Usage:

When a pull request is created or edited, the workflow automatically triggers.

The workflow checks for:

A non-empty PR description.
A valid issue reference format (Fixes , Close, Closes, Closed , Fix , Fixed , Resolve , Resolves #Issue_number).

If either check fails, the PR will be marked as failing, and the author will receive clear error messages in the PR comments.
If all checks pass, a confirmation message will indicate that the PR is valid.

Note: Kindly add all the labels added to the issue, to this PR!
@TejasNasre

kya ho raha hai explain this actions bro

It shows the PR is tagged to a issue or not! @TejasNasre

update this PR now

@smog-root sir join vc gssoc

Add labels!!

Level2 with gssoc-ext and hacktoberfest-accepted!!

And assign me!


Alpine image for minimal size

I would love to have this for couchDB. Currently, the images sizes are too big.

Yeah that would be lovely. Would you want to work on this?

I would love to but unfortunately I don't have experience in installing couchDB. From what I understand from the other files, it doesn't look as straight forward as possible.

yeah, I think I looked into it a while back, but couldn't get erlang to run or something. Don't quite remember

There is an erlang alpine image now.

@pksunkara yeah, img size is huge (over 350 MB) but it seems erlang is pretty space hungry: building erlang under alpine linux (using kerl) results ~150 MB release dir. So I'm curious to know how much space can be actually saved with alpine linux.
I did some work on building couchdb2 in alpine (copypasta, not script/Dockerfile). It compiles, I didnt test it further (yet).

Just a little update... It seems trivial to bring features on par with Debian image. That's not the problem. But I have some issues which effectively stalled my work. I don't really see it viable to ship official Alpine CouchDB anytime soon.
mozjs185
The root of all issues: mozjs185 is from 2011. No upstream patches since then. GCC 6 can't compile original codebase.
Alpine releases
Coincidentally, the latest Alpine (3.5) ships with GCC 6 & co. When looking Alpine´s release policy, they offer only 2 year maintenance cycle. Targeting to old version is not option there.
mozjs from Debian / Fedora
Both Debian and Fedora have custom patched versions, they ship with GCC 6 so they have patch for that too. I glanced both, I got a bit confused and even suspicious how their patching works. I tried to track down how Debian build tools do it but I didn't find the answer. It may be that Busybox's patch & co are missing some option. I thought I should open Stackoverflow question about it but haven't done so yet. Anyway, I couldn't find clean way to apply their patches. I could do it manually one by one but I'd prefer to know what I'm mimicking if doing so.
Replace mozjs?
At some point, I tracked down why CouchDB is still using ancient version of SpiderMonkey. And is there any plans to upgrade / replace it? Node.js version is even mentioned in documentation somewhere, but if I'm right, the idea was shut down around 2013. Also, I remember python version mentioned somewhere.
Surprisingly, just a day or two later, @dmunch's couch-chakra popped up. Since my alpine build wont be stable/prod-ready anytime soon, I might as well try to build it with chakra version. I don't know how realistic that plan that is, but I think I'll try at some point. I glanced chakra-core docs/src, and I didn't notice any immediate showstopper.

While I don't wont to dis-encourage you to replace mozjs I want to stress that couch-chakra really is in its very early stages. ChakraCore itself had its first release with full JIT support on Linux/Mac in December 2016 so nobody really knows how it behaves in the wild. As for couch-chakra, the only thing it ever ran was the test-suite for the query server protocol, I actually never ran it for processing a "real-life" view function.
I would of course be all for driving couch-chakra further and would be more than happy to see it used in the wild and would voluntarily give a helping hand in building, debugging and doing whatever it needs to get it to work. I just want to stress that, by choosing this route, you're potentially going down a deep rabbit hole transporting you light years form the the initial issue :)

@dmunch  Your readme makes things pretty clear but good that it's said explicitly here too: My previous post means, I abandoned idea of Alpine based CouchDB 2.0 image. I'm not going to complete it as it is. If I continue that project, it will be something really, really, experimental. Or I simply wait.
Debian & RH/Fedora teams are maintaining legacy mozjs package: if you want to use current CouchDB, use their package. That's what I will be doing..

Wow, this has been super interesting to follow 😊 I really hope CouchDB is going to start using a more modern js runtime or just drop the concept of a view server and make everything declarable via mango or something similar.
Anyways, I'm going to close this issue as an Alpine image doesn't seem possible.


Caddy - Unexpected behavior on path having the right -login-path prefix, but other characters following it

When using Caddy, if you use default -login-path being /login I created a table with current behavior and what I believe are expected behavior:

Test no
Path
Current behavior
Expected behavior

1
/login
Displays login page
Displays login page

2
/LOGIN
Displays login page (if CASE_SENSITIVE_PATH stays "false" which is default) otherwise returns a 404
Displays login page (if CASE_SENSITIVE_PATH stays "false" which is default) otherwise displays a login page

3
/loginz
Displays login page
404

4
/login/
Displays login page
404

5
/login/z
Displays login page
404

6
/loginz/z
Displays login page
404

(*) I'm not 100% sure on behavior for test 2 as I tested on Windows 7 x64 and this OS isn't case sensitive. It would need to be confirmed on another OS.
I think this should be adjusted for Caddy and probably for loginsrv by itself as well.
I think these lines could be adjusted :
Caddy https://github.com/tarent/loginsrv/blob/7a8566d795ccd0337dbd35078817f06ae5edccb1/caddy/handler.go#L42
loginsrv by itself https://github.com/tarent/loginsrv/blob/7a8566d795ccd0337dbd35078817f06ae5edccb1/login/handler.go#L78
@smancke I'll submit a PR for Caddy you can review.
This change would be a change of behavior and should be mentioned in next version if it is modified.

Hi @magikstm the login path is by design a prefix.
This is used e.g in case if oauth flows, e.g. /login/google etc.

But maybe it would make sense to return a 404 for the cases 3 and 6.
So only allow /login and all sub ressources ..?


[WATCHLIVE]HSF! Chaminade-Madonna vs Blanche Ely LIVE Ｂｒｏａｄｃａｓｔ Ｆｒｅｅ ＯＮ Ｔｖ Ｃｈａｎｎｅｌ 30． ０８． ２０２４

How to watch Chaminade-Madonna vs Blanche Ely Live: High School Football Live and TV guide, team news, kickoff time, predictions, live Online.
🔴📺 GO LIVE==►► CLICK HERE TO WATCH LIVE

🔴📺 STREAMING==►► CLICK HERE TO WATCH LIVE

There is a complete guide to watch High School Football live online from anywhere? How to watch it free and what tv channel will broadcast in your area and HS Football Game Guide.
High School Football is one of the most spectacular High School sports events in the United States of America. It is the most prestigious High School championship game in the United States. US people around the will watch the most pivotal game in the High School Football season.
Here we are going to share with you the ways to watch High School Football 2024 online. For the cord-cutters, you will have peace of mind since you could reserve your options to follow the game now.
High School Football 2024 Official tv Channel Coverage
The High School Football will be held at August 2024 and NFHS Network will cover the full High School Football Game from the. Watch games live and on-demand on NFHSnetwork. Plus you can watch highlights, find games of the week, and watch other events such as graduations and non sports events. Watch games live and on-demand on the NFHS Network app.
How to Watch the High School Football 2024 Live Stream in the United States
NFHS Network is the official broadcaster of the High School Football in the US. It will be available for live streaming online. You could visit NFHS Network’s official site to watch it live stream on your PC or laptop. Or, you could download the app to watch the NFHS Network App on your mobile devices, including smartphones and tablets.
How to Stream High School Football Online Using Cable?
The High School Football is covered by NFHS Network. If you subscribe to cable TV, all you need to do is tune into NFHS Network to watch the event from beginning to end.
How to Watch High School Football 2024 Live Online
Watching High School Football 2024 without cable is feasible for all folks. After all, you don’t have to pay for expensive cable or satellite subscription. There could be a chance that you have left your cable or satellite. For the cord cutters, you can watch High School Football live online without cable.
How is that even possible? You might have sort of question. Well, it is very possible with the help of the live streaming option.
There are a lot of live streaming options available online. It could take time and effort to find out the best one for you. Instead, take a look at our recommended list below.
FuboTV
FuboTV has been one of the most prominent live streaming options for sport lovers. Introduced as the Football live streaming providers, it has been evolving from time to time to manage the sport content in a wider variety. That also includes the High School Football niche in its package. the live streaming service is available in many territories and compatible with various devices. It is simple and straightforward to use the service with the tips of your fingers. NBC Sports and FOX Sports are available in the package. It also comes with free trial offers in case you’d like to assess the service first.
Youtube TV
YouTube TV can be much familiar to you if you have been using YouTube platform for a while. Although it is a relatively new player in the market, the feedback from its customers are awesome. People love this service because the quality is excellent with considerable price. With only $45 per month, you will get the full pack of the live streaming service including the channels that broadcast the High School Football. it also comes with the free trial offers which you can use to assess the quality of service. The free trial is eligible for new users only.
PlayStation Vue
PS Vue is not only prevalent choice for the console owners. Regardless of the name, it is a live streaming service for public. Everyone can use the service because PS Vue comes with many devices compatibility. Consider to check the list of compatibility first before proceeding to see if your device is compatible with the service or not. If you are not really sure, you could use its 5-day free trial to assess the quality of service and watch some of the matches of High School Football for free. Tune into the NBC Sports or Fox Sports to see the coverage.

IYOWIKJCSZXSA

ftyf

📺📱 Chaminade-Madonna vs  Blanche Ely
📺📱 Chaminade-Madonna vs  Blanche Ely
📺📱 Chaminade-Madonna vs  Blanche Ely
▶
➤►
➤►
▶
➤►
📺📱 Chaminade-Madonna vs  Blanche Ely
📺📱 Chaminade-Madonna vs  Blanche Ely
➤►
▶
➤►
➤►
▶
➤►
➤►
▶
➤►
📺📱 Chaminade-Madonna vs  Blanche Ely
📺📱 Chaminade-Madonna vs  Blanche Ely
➤►
▶
➤►
➤►
▶
➤►
➤►
▶
➤►
📺📱 Chaminade-Madonna vs  Blanche Ely
📺📱 Chaminade-Madonna vs  Blanche Ely
➤►
▶
➤►
📺📱 Chaminade-Madonna vs  Blanche Ely
📺📱 Chaminade-Madonna vs  Blanche Ely
➤►
▶
➤►


Add my script.

Feature:

Auto detect & download latest release;

Auto detect CPU architecture.

Auto reload.

TODO:
Add interactive options to determine whether to run frps/frpc services on startup.

Plan to add exception handling in next morning.

Can you rebase all commits into one?

Rebased.

I think you should fix it

Looks great script! Could we merge it now?


Re-interrupt current thread when ignoring InterruptedException

R: @lukecwik

Need to resolve merge conflicts.

merged with master

LGTM


Look in the checked directory for a config

Duplicate of https://github.com/sinetoami/nmcli-rofi/commit/bb89f8b03051dc3729e632ff6612add81f0fd112


updateContentTypeInMeiliSearch duplicates lifecycle methods

Description
Based on my experience with the Meilisearch plugin, it appears that multiple invocations of the service updateContentTypeInMeiliSearch method (which adds all entries from a contentType) cause each index update to be executed as many times as the addContentTypeInMeiliSearch method has been called since the server was started.  I suggest adding a check to skip lifecycle subscriptions if the contentType has already been added. This could prevent the duplication of lifecycle methods and ensure that each index update is only executed once.
Environment:

OS: Windows 10
strapi-plugin-meilisearch version: 0.12.0
Strapi version: 4.24.2

I was going to post the same issue.
Moreover, when you update the index from the plugin settings with the "update" button. It duplicates the subscription too.


Fix array serialization

Fixes https://github.com/electric-sql/pglite/issues/220

@samwillis Is there a better way to run tests than this? This way is slow and quite painful:
pnpm build && pnpm exec vitest run -t 'basic esm array params' tests/basic.test.js

I cleaned it up and I think it's a bit better now. Let me know if you have any suggestions!

Thanks for picking this up @alexgleason!
It's the end of the day for me here and so I'll take a proper look in the morning. I don't suppose you could just jot down the strategy you've gone with, from a quick glance (on my phone cooking dinner) I didn't quite follow what fixedParams was doing. Is this influenced by any other JS Postgres's clients?

@samwillis After sending Parse, we now send a Describe (S type) to get parameter info from Postgres.
I loop through parsedParams, and if the oid we inferred with JS code doesn't match the oid Postgres gave us, I re-parse it with the new oid. Then fixedParams gets passed down instead of parsedParams.

I published this branch to<EMAIL_ADDRESS>pulled it into my tests, and would you look at that:

Finally able to use pglite in my application.

Hey @alexgleason
This is great, I really like the strategy of asking PG what the types of the params should be.
I want to spend some time refactoring the type support, and will use this as the base. Plan for early next week.

I updated this to remove the unnecessary JS type inference code I added. So it's simpler now, and still works perfectly.
I think this is probably acceptable to merge, as there is not much baggage. I would say optionally the function serializeType in types.ts could be removed, but it's still used by serializeArray, which I think is fine.
@samwillis if you have any specific gripes feel free to give me a scathing review like I'm you're employee. I have time to fix it, and match your preferred code style etc. Since PGlite is also required for my goals (which is my full time job). I just need to get it in a place where everything works right in my project, then it's done. I also need your help with https://github.com/electric-sql/pglite/issues/327 but I think it makes sense to do this one first.

Thank you very much @samwillis !

Closing in favour of #340 which is based on this but with a larger refactor.


Assign countries from member page

It is possible to assign members from country pages, but it should also be possible to assign countries from member pages. I think the <NTransfer /> component would work well, but we can also just stick with <Select />.

Closed due to a incident with Github, see #17 for original.


Error(s) in loading state_dict for Wav2VecModel:

🐛 Bug
I receive message 'Error(s) in loading state_dict for Wav2VecModel:' with wav2vec_small.pt
I also tried wav2vec_big_960h.pt and got a similar error.
I have searched issues but don't find any info.
To Reproduce
I follow the example code here
wget -c https://dl.fbaipublicfiles.com/fairseq/wav2vec/wav2vec_small.pt

import torch
from fairseq.models.wav2vec import Wav2VecModel

cp = torch.load('wav2vec_small.pt')
model = Wav2VecModel.build_model(cp['args'], task=None)
model.load_state_dict(cp['model'])
model.eval()

Here is my stack trace
RuntimeError                              Traceback (most recent call last)
<ipython-input-9-8b7e23d59ca9> in <module>()
      4 cp = torch.load('wav2vec_small.pt')
      5 model = Wav2VecModel.build_model(cp['args'], task=None)
----> 6 model.load_state_dict(cp['model'])
      7 model.eval()

1 frames
/content/fairseq/fairseq/models/fairseq_model.py in load_state_dict(self, state_dict, strict, args)
     94         self.upgrade_state_dict(state_dict)
     95         new_state_dict = prune_state_dict(state_dict, args)
---> 96         return super().load_state_dict(new_state_dict, strict)
     97
     98     def upgrade_state_dict(self, state_dict):

/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py in load_state_dict(self, state_dict, strict)
   1043         if len(error_msgs) > 0:
   1044             raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
-> 1045                                self.__class__.__name__, "\n\t".join(error_msgs)))
   1046         return _IncompatibleKeys(missing_keys, unexpected_keys)
   1047

RuntimeError: Error(s) in loading state_dict for Wav2VecModel:
	Missing key(s) in state_dict: "feature_extractor.conv_layers.1.2.weight", "feature_extractor.conv_layers.1.2.bias", "feature_extractor.conv_layers.2.2.weight", "feature_extractor.conv_layers.2.2.bias", "feature_extractor.conv_layers.3.2.weight", "feature_extractor.conv_layers.3.2.bias", "feature_extractor.conv_layers.4.2.weight", "feature_extractor.conv_layers.4.2.bias", "feature_extractor.conv_layers.5.2.weight", "feature_extractor.conv_layers.5.2.bias", "feature_extractor.conv_layers.6.2.weight", "feature_extractor.conv_layers.6.2.bias", "feature_aggregator.conv_layers.0.1.weight", "feature_aggregator.conv_layers.0.1.bias", "feature_aggregator.conv_layers.0.3.weight", "feature_aggregator.conv_layers.0.3.bias", "feature_aggregator.conv_layers.1.1.weight", "feature_aggregator.conv_layers.1.1.bias", "feature_aggregator.conv_layers.1.3.weight", "feature_aggregator.conv_layers.1.3.bias", "feature_aggregator.conv_layers.2.1.weight", "feature_aggregator.conv_layers.2.1.bias", "feature_aggregator.conv_layers.2.3.weight", "feature_aggregator.conv_layers.2.3.bias", "feature_aggregator.conv_layers.3.1.weight", "feature_aggregator.conv_layers.3.1.bias", "feature_aggregator.conv_layers.3.3.weight", "feature_aggregator.conv_layers.3.3.bias", "feature_aggregator.conv_layers.4.1.weight", "feature_aggregator.conv_layers.4.1.bias", "feature_aggregator.conv_layers.4.3.weight", "feature_aggregator.conv_layers.4.3.bias", "feature_aggregator.conv_layers.5.1.weight", "feature_aggregator.conv_...
	Unexpected key(s) in state_dict: "encoder.pos_conv.0.bias", "encoder.pos_conv.0.weight_g", "encoder.pos_conv.0.weight_v", "encoder.layers.0.self_attn.k_proj.weight", "encoder.layers.0.self_attn.k_proj.bias", "encoder.layers.0.self_attn.v_proj.weight", "encoder.layers.0.self_attn.v_proj.bias", "encoder.layers.0.self_attn.q_proj.weight", "encoder.layers.0.self_attn.q_proj.bias", "encoder.layers.0.self_attn.out_proj.weight", "encoder.layers.0.self_attn.out_proj.bias", "encoder.layers.0.self_attn_layer_norm.weight", "encoder.layers.0.self_attn_layer_norm.bias", "encoder.layers.0.fc1.weight", "encoder.layers.0.fc1.bias", "encoder.layers.0.fc2.weight", "encoder.layers.0.fc2.bias", "encoder.layers.0.final_layer_norm.weight", "encoder.layers.0.final_layer_norm.bias", "encoder.layers.1.self_attn.k_proj.weight", "encoder.layers.1.self_attn.k_proj.bias", "encoder.layers.1.self_attn.v_proj.weight", "encoder.layers.1.self_attn.v_proj.bias", "encoder.layers.1.self_attn.q_proj.weight", "encoder.layers.1.self_attn.q_proj.bias", "encoder.layers.1.self_attn.out_proj.weight", "encoder.layers.1.self_attn.out_proj.bias", "encoder.layers.1.self_attn_layer_norm.weight", "encoder.layers.1.self_attn_layer_norm.bias", "encoder.layers.1.fc1.weight", "encoder.layers.1.fc1.bias", "encoder.layers.1.fc2.weight", "encoder.layers.1.fc2.bias", "encoder.layers.1.final_layer_norm.weight", "encoder.layers.1.final_layer_norm.bias", "encoder.layers.2.self_attn.k_proj.weight", "encoder.layers.2.self_attn.k_proj...

Code sample
See above
Expected behavior
Model should load cleanly.
Environment
Google Colab

fairseq Version (e.g., 1.0 or master): master
PyTorch Version (e.g., 1.0): 1.6.0+cu101
OS (e.g., Linux): Google Colab (Linux)
How you installed fairseq (pip, source): source
Build command you used (if compiling from source): pip install --editable ./
Python version: 3.6.9
CUDA/cuDNN version: Unknown
GPU models and configuration: Unknown
Any other relevant information:

It seems to work if I use this code:
checkpoint = torch.load(fname)
args = checkpoint["args"]
model = Wav2VecModel.build_model(args, None)
#model.load_state_dict(checkpoint["model"])
model.load_state_dict(checkpoint["model"], strict=False)

which I found in here: https://github.com/pytorch/fairseq/issues/2495
Is this correct? Could it be explained/documented? The code in the example/README.md doesn't work

Hi All,
I had the same error message issues when loading the same pre-trained model wav2vec_small_960h.pt downloaded
I tried to load it in a finetune-ctc stage as described into example/README.md.
Looking at error messages, it seems that there is a conflict between dictionaries: the one present into the downloaded checkpoint, and the one defined into the current model.
RuntimeError: Error(s) in loading state_dict for Wav2VecCtc:
size mismatch for w2v_encoder.proj.weight: copying a param with shape torch.Size([32, 768]) from checkpoint, the shape in current model is torch.Size([512, 768]).
size mismatch for w2v_encoder.proj.bias: copying a param with shape torch.Size([32]) from checkpoint, the shape in current model is torch.Size([512]).
The last random layer added by wav2vec_ctc model on top of the unsupervised stage, has a mismatch: 32 versus 512.
The dictionary I used is the letter one (letters plus word boundary char).
Any comments? Am I using the right pre-trained model?
Let me try the fix above #2495..

w.r.t. examples/README.md guirdeline, ctc finetune works when I use

wav2vec_small.pt as --w2v-path, and
wav2vec_small_960h.pt as "latest checkpoint".
In practice, in the ctc finetune is like I should do some extra iteration with pre-trained model.

I was using wav2vec_small_960h.pt as --w2v-path.

the checkpoint you are trying to load is a wav2vec 2.0 model ("wav2vec_small.pt"). but the model you are trying to load it INTO is a wav2vec 1.0 model. try creating a wav2vec 2.0 model instead:
>>> import torch
>>> from fairseq.models.wav2vec.wav2vec2 import Wav2Vec2Model
>>> from fairseq.dataclass.utils import convert_namespace_to_omegaconf
>>> cp = torch.load('/private/home/abaevski/models/wav2vec2/wav2vec_small.pt', map_location='cpu')
>>> model = Wav2Vec2Model.build_model(convert_namespace_to_omegaconf(cp['args']).model, task=None)
>>> model.load_state_dict(cp['model'])
<All keys matched successfully>

@alexeib correct is what I ended up doing. I was feeling confused that all the variations (1.0 model 2.0 checkpoint and 2.0 model 2.0 checkpoint) required strict=False---why doesn't 2.0 checkpoint load without strict for 2.0 model?---but mixing 1 and 2 didn't make sense to me. Sorry for not closing the issue.
If you are curious, one our pitch benchmark we found that 2.0 LV-60 no-fine-tuning with 2.0 wav2vec model actually had very similar scores as 2.0 small no-fine-tuning with 1.0 wav2vec.

it is better to load it like this:
model, cfg, task = fairseq.checkpoint_utils.load_model_ensemble_and_task(['/path/to/checkpoint.pt'])
re: results, trying using transformer layers other than the last one (you will have to modify code to do this)

This is what I tried according to REAME:
HYDRA_FULL_ERROR=1 python fairseq_cli/hydra_train.py \
    task.data=/dataset/timit/data/ \
    model.w2v_path=/dataset/libri960_big.pt \
    distributed_training.distributed_world_size=0 \
    +optimization.update_freq='[24]' \
    --config-dir examples/wav2vec/config/finetuning/ \
    --config-name base_960h

I tried the combination of model.w2v_path=wav2vec_big_960h.pt and --config-name vox_960h or --config-name base_960h. And here is what I've got at every attempts:
  ...
  File "/app/fairseq/models/wav2vec/wav2vec2_asr.py", line 147, in build_model
    w2v_encoder = Wav2VecEncoder(cfg, task.target_dictionary)
  File "/app/fairseq/models/wav2vec/wav2vec2_asr.py", line 302, in __init__
    model.load_state_dict(state["model"], strict=True)
  File "/app/fairseq/models/fairseq_model.py", line 115, in load_state_dict
    return super().load_state_dict(new_state_dict, strict)
  File "/opt/bitnami/miniconda/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1052, in load_state_dict
    self.__class__.__name__, "\n\t".join(error_msgs)))
RuntimeError: Error(s) in loading state_dict for Wav2VecCtc:
        size mismatch for w2v_encoder.proj.weight: copying a param with shape torch.Size([32, 1024]) from checkpoint, the shape in current model is torch.Size([43, 1024]).
        size mismatch for w2v_encoder.proj.bias: copying a param with shape torch.Size([32]) from checkpoint, the shape in current model is torch.Size([43]).

As @alexeib pointed out earlier, had I accidentally loaded the checkpoint to wav2vec 1.0 model? But as I can see, the firstline off logs is wav2vec2_asr.py, so it's probably v2.0.
Or should I write a python script for it?


Maybe type classes

Hi I enjoy using this library. It's really reduced a lot of boilerplate for me, so thanks so much for putting it together!
One thing that I wish it had out of the box is type class instances for Maybe. Using NullOrUndefined feels a bit leaky to me, and wrapping my Maybes in newtypes just to get the functionality I wanted was becoming fairly tedious since I use Maybe so much. I also noticed there some similar sentiment on the latest PureScript Unscripted, so I decided to make this PR.
Things to note:

when reading json, fields with Maybe types that have corresponding json values that are null or undefined will decode to a Nothing. Otherwise it will be Just value
when writing fieldName :: Just value to json, the resulting json will be "fieldName":"value", and when writing fieldName :: Nothing, the resulting json will be "fieldName":null
I've added a foreign import to allow null to be written to the resulting json, and because I did that I didn't want it leaking out of the module, so I've added all of the relevant functions as exports.
I've added four additional tests to test the edge cases and standard cases.

Hope that you find this helpful. If you'd like any changes, I'm happy to make them!

done! travis should be doing it's work any moment
On Thu, Sep 21, 2017 at 1:58 PM, Justin Woo<EMAIL_ADDRESS>wrote:

@justinwoo commented on this pull request.
In src/Simple/JSON.purs
https://github.com/justinwoo/purescript-simple-json/pull/16#discussion_r140315536
:

@@ -143,6 +166,12 @@ instance writeForeignArray :: WriteForeign a => WriteForeign (Array a) where
instance writeForeignNullOrUndefined :: WriteForeign a => WriteForeign (NullOrUndefined a) where
writeImpl (NullOrUndefined a) = maybe undefined writeImpl a

+instance writeForeignMaybe :: WriteForeign a => WriteForeign (Maybe a) where

writeImpl (Just a) = writeImpl a
writeImpl Nothing = null

+foreign import null :: Foreign
Ah, null isn't exposed by Nullable but really, I'd even prefer toForeign
$ toNullable Nothing
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/justinwoo/purescript-simple-json/pull/16#discussion_r140315536,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACCoXCc0i_ruMA6N2F0OXEi06emueODks5skqOvgaJpZM4Pexyq
.

Merged, thanks!


nearest station based on transport type

What would also be nice is to get the nearest station based on the station type. For example, the nearest SBAHN station.
Something like this maybe:
async def nearby_async(latitude: float, longitude: float, transport_type: TransportType = None) -> dict[str, str] | None:

    try:
        args = dict.fromkeys(Endpoint.FIB_NEARBY.value[1])
        args.update({"latitude": latitude, "longitude": longitude})
        result = await MvgApi.__api(Base.FIB, Endpoint.FIB_NEARBY, args)
        assert isinstance(result, list)

        # return first location of type "STATION"
        for location in result:
            if transport_type == None:
                station = {
                    "id": location["globalId"],
                    "name": location["name"],
                    "place": location["place"],
                }
                return station
            elif str(transport_type.name) in location["transportTypes"]:
                station = {
                    "id": location["globalId"],
                    "name": location["name"],
                    "place": location["place"],
                }
                return station
        # return None if no station was found
        return None

Originally posted by @jannikobenhoff in https://github.com/mondbaron/mvg/issues/3#issuecomment-1633197662

The API does not support a native option to filter by transport type. Instead, I just added the option to retrieve the full list of nearby stations, as suggested in https://github.com/mondbaron/mvg/issues/3, which leaves the (optional) filtering to the user.


Automate Laravel mail config

The Issue
Laravel requires additional configuration to work with DDEV's Mailhog.
How This PR Solves The Issue
This PR add MAIL_HOST=<IP_ADDRESS> to the project's .env.
Manual Testing Instructions

Follow quickstart guide for a Laravel project.
Enter REPL mode

ddev artisan tinker

Send a test mail which should be caught by Mailhog.

Illuminate\Support\Facades\Mail::raw('Hello World!', function($msg) {$msg->to('example@example.com')->subject('Test Email'); });

Type exit to escape from REPL mode.

Related Issue Link(s)
Fixes #4821
Release/Deployment Notes
Recent versions of DDEV automate the database settings, so it seems consistent to include the mail server.
Developers are free to opt out of DDEV managing this using currently documented best practises.

It doesn't look like the "send email" instructions are adequate for a novice like me to manually test. Can you add more detail about how to do it? Thanks!

I updated the description to try and make it simpler.  As long as you have a working Laravel install, you should be able to enter "tinker mode" (REPL). REPL allows you to run PHP commands in a bootstraped environment.
The command in the description tries to send an email; it it should be a simple copy/paste.
Let me know if you are getting a specific error message.

I have a ddev artisan command in my global commands. It has the #ddev-generated so I assume it's in the standard install right?

That also means the quickstart could use it instead of ddev exec

Added

https://github.com/ddev/ddev/pull/4822

Sorry I haven't tested yet, will get to it!


Question: Difference between this library and native cache property

https://facebook.github.io/react-native/docs/image.html
Hi there! I was just wondering if there is a difference between this library and specifying cache: 'only-if-cached' on an <Image/> component.

@clemmy, the cache attribute didn't exist at the time I wrote the package. I will try to use it and see if I can get the same UX quality than with react-native-img-cache and let you know. Thank you for pointing that out.

@clemmy I added a comment in the README, let me know if it makes sense or not.

Thanks :)


hotfix: Changes in layout and theme analytics events (#17827)

(cherry picked from commit 31b03e893914a23fc9771acca72937d588319174)
Description
Cherry-picked changes for corrected Analytics event for page updates

/ok-to-test sha=ceac6b31085b484502315375116b8cd013f44c8f


Treat reaching the maximum parse depth as EOF

The parser is fragile and hitting the maximum tree depth has exposed several bugs. By treating this condition as if it is an EOF means that we're back in the normal parsing condition.
This does expose a weakness in Gumbo's design: A spec bug that results in skipped steps or failure to reprocess a token (or if we fail to implement the spec in such a way), then the result can be crashes. Not ideal.
Fixes: oss-fuzz-66107

What problem is this PR intended to solve?
oss-fuzz-66107

Have you included adequate test coverage?
Nope! I'm sorry to punt on testing again but I didn't take the time to understand why this bug occurred so I didn't produce a minimal test case. Treating hitting the max depth as EOF just seemed like the best way to fix this whole class of bugs by turning the exceptional (> max depth) parsing case into the normal parsing case.

Does this change affect the behavior of either the C or the Java implementations?
C

@stevecheckoway Thank you! No sweat on the testing; I feel like things the fuzzer finds aren't always great to add to a functional test suite, anyway.
I manually tested this branch against the fuzzer repro and it looks great! :heart:


Use float for GridPos values

fix for issue #168.
GridPos struct use float64 + test case for int & float values

Merged. Thanks!


"anyOf" and "oneOf" give incorrect error message

Using "anyOf" or "oneOf" gives an incorrect message by always indicating the the attribute defined in the first index of the anyOf or oneOf array is required.
Given the following schema:
{   "$schema":"http://json-schema.org/draft-07/schema#",   "$id":"test.schema.json",   "title":"test",   "type": "object",   "properties": {     "options": {       "type":"object",       "anyOf": [         {"required": ["one"]},         {"required": ["two"]}       ],       "properties":{         "foo": {           "type":"object"         },         "bar": {           "type":"object"         }       }     }   } }
and the following JSON
{   "options":{       "foo":{}     } }

Expected Results:
Generated at https://www.jsonschemavalidator.net/

Actual Results:
Code used to validate and show errors reported:
result, err := gojsonschema.Validate(schemaLoader, requestLoader) if !result.Valid() {   for _, err := range result.Errors() {     log.Println()   } }
Actual Error Message:
options: Must validate at least one schema (anyOf)
layers: one is required

Error messages for anyOf and oneOf are tricky as it's not always as clear what the error message should be. If you have multiple clauses in a oneOf and none of them pass and then put all errors of all clauses in the resulting error set that can lead to a massive amount of errors. Most of those errors will be nonsense as only one of them needs to be satisfied, and in the case of oneOf, satisfying too many will lead to a different error.
Therefore the original author chose to only return one single error for anyOf and oneOf by heuristically looking for the clause that matched most closely (has the least amounts of errors), and only return the errors from that clause. However in practice (and also your example), all clauses are equally unsatisfied and therefore the first one is chosen.
Most implementations, like https://www.jsonschemavalidator.net/ do this differently.  I'm not sold on the way it's currently done in gojsonschema, but I don't hate it either. If anyone convinces me that this really should be changed and submits a PR I'm open to it.

See also json-schema-org/json-schema-spec#643 and json-schema-org/json-schema-spec#632


The generate sitemap  is wrong(inaccuracy)!

The hexo-generator-sitemap plugins generated sitemap.xml that <lastmod> corresponding the last modification time of the source folder file , but the <lastmod> should corresponding the last modification time of the html file.
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>http://www.example.com/foo</loc>
    <lastmod>2018-06-04T18:00:15+00:00</lastmod> <!--The time last modification of the `foo.html`.-->
  </url>
</urlset>

I found [GSC Help] have a tips:

Google reads the <lastmod> value, but if you misrepresent this value, we will stop reading it.

source: Manage your sitemaps: Build and submit a sitemap

If the sitemap <lastmod> is wrong, meaning the sitemap not effect?
About lastmod

append in 2020.04.16:
Because my sitemap cann't be read by GSC, I guess may be caused by the wrong <lastmod>.

It cause my article cann't be indexed in time. Almost need a week!
Your sitemap can be read in GSC? Your posted article can be searchable in next day?
If your sitemap can be read, and the <lastmod> don't inconsistent, So the <lastmod> don't matter in sitemap!
If your sitemap can not be read, but your posted article can be searchable in next day. Please reply me, I need your help.

you can modify sitemap.xml or create external template as your own demand. Like this:
post.updated.toISOString().substring(0, 10)
Hope it will help you

@flashlab @DeppWang
If you guys are sure there is something wrong with  lastmod, feel free to open a new pull request.

@flashlab
Thanks, ask a question: Your sitemap can be read in GSC?

@flashlab I found your article can be indexed in time. Ask a question: Your sitemap can be read in GSC?

@DeppWang @SukkaW tested myself
Please check #94

@SukkaW I found your article can be indexed in time. Ask a question: Your sitemap can be read in GSC?

@flashlab
May be can use a sitemap_template.xml replace time to date, don't need change to source code.

You can check your GSC, if your sitemap can be read. So the  is not a issue.
If  is a issue. Can't to change  solove it, need to get html file last modification time, or remove .

2018-06-04T18:00:15+00:00 does conform to the W3C Datetime/ISO 8601 format as specified by the protocol.
Perhaps Google expected 2018-06-04T18:00:15.000Z which should be the format generated by this plugin.
Can I have your Node version and "package.json"? Output of $ node -v and $ npm ls --depth 0?
In the meantime, I'll check my GSC.

@curbengh , Thanks your reply.

2018-06-04T18:00:15+00:00 was copied from protocol. My sitemap.xml <lastmod> format is like 2018-06-04T18:00:15.000Z. I didn't notcie the difference of both(a mistake). I rather express the difference between the local md file last modified time and online html file last modified time. May be the difference don't matter. My sitemap.xml: https://depp.wang/sitemap.xml. After test: Even though I remove the <lastmod> of sitemap.xml, the GSC also can't read my sitemap.xml.

I use hexo-aciton deploy blog, this is the hexo env. I don't think it's related to env.

I first added my site to GSC in 2017.

I guess it may be that the weight of my site is too low, so GSC does not read my sitemap.xml. Now, Google Spider should indexes my articles through the homepage, so it very slow.
Your sitemap.xml can be read in time?

My sitemap.xml: https://depp.wang/sitemap.xml

I notice all <lastmod> values are the same, which I think is the deployment time. Perhaps GSC finds it unusual and ignore it.
I have two suggestions (you can try all):

Use post.date only, this requires custom template.

Add the following content to "source/.sitemap.xml":

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  {% for post in posts %}
  <url>
    <loc>{{ post.permalink | uriencode }}</loc>
    {% if post.date %}
    <lastmod>{{ post.date.toISOString().substring(0, 10) }}</lastmod>
    {% endif %}
  </url>
  {% endfor %}
</urlset>

Configure this plugin to use the above sitemap:

_config.yml
sitemap:
  template: ./source/.sitemap.xml

GSC also supports RSS. Install hexo-generator-feed and add https://depp.wang/atom.xml to GSC. Do not remove sitemap from GSC.

@flashlab

This step I had done. Because I use github action deploy blog, the action env will clone all files again each time. so the lastmod are the same. There is no good way to solve this issue.
I had added atom.xml to GSC, follow your suggestion.

Thinks your suggestions.

the action env will clone all files again each time. so the lastmod are the same.

My suggested template doesn't use post.updated; it only uses post.date (derived from a post's front matter) so "lastmod" should be unique.

I didn't notice the details, I have updated it.
Thanks very much!

https://github.com/hexojs/hexo-generator-sitemap/pull/94, released in 2.1.0.

@curbengh Hi, I am coming again 😂, same old problem.  atom.xml still "Coun't fetch" .

GSC said they can use the Atom 1.0 or RSS 2.0 as a sitemap, My atom.xml  is Atom 1.0,  I check the format is right. It is possible that I use the Cloudfare as a DNS causing it? I have no idea. I try to feedback to google support, but no reply.
What direction shou I take to check for error? Can you give me a suggestion, thx.

I use Cloudflare as well and my atom.xml issue resolved itself within a few days. Can you access to http://yoursite.com/atom.xml.gz? Alternative is to switch to RSS format and try again.

My https://depp.wang/atom.xml.gz can't access, your site atom.xml.gz can download the xml. I will try to use the RSS, hope it can useful. Thanks for your reply.


Can not compile from the makefile

Hi,
I have installed the SGX sdk and drivers but I cannot build from the makefile. What's the gcc and g++ version did you use?
Thanks,

I fixed the problem with gcc-7 and g++-7.


model from google drive.

Could you upload the model to google drive?
I don't have a Baidu account.

Hi. We have upload it.

Thanks!