netlify dev --live

I have this error
◈ Installing Live Tunnel Client
/usr/lib/node_modules/netlify-cli/node_modules/netlify-redirector/lib/redirects.js:116
      throw ex;
      ^

TypeError: Cannot read property 'objectMode' of undefined
    at Source.Writable.write (/usr/lib/node_modules/netlify-cli/node_modules/decompress-tar/node_modules/readable-stream/lib/_stream_writable.js:317:22)
    at Extract._write (/usr/lib/node_modules/netlify-cli/node_modules/decompress-tar/node_modules/tar-stream/extract.js:230:21)
    at Extract._continue (/usr/lib/node_modules/netlify-cli/node_modules/decompress-tar/node_modules/tar-stream/extract.js:213:28)
    at oncontinue (/usr/lib/node_modules/netlify-cli/node_modules/decompress-tar/node_modules/tar-stream/extract.js:68:10)
    at Extract.onheader [as _onheader] (/usr/lib/node_modules/netlify-cli/node_modules/decompress-tar/node_modules/tar-stream/extract.js:183:5)
    at Extract._write (/usr/lib/node_modules/netlify-cli/node_modules/decompress-tar/node_modules/tar-stream/extract.js:250:8)
    at doWrite (/usr/lib/node_modules/netlify-cli/node_modules/decompress-tar/node_modules/readable-stream/lib/_stream_writable.js:428:64)
    at writeOrBuffer (/usr/lib/node_modules/netlify-cli/node_modules/decompress-tar/node_modules/readable-stream/lib/_stream_writable.js:417:5)
    at Extract.Writable.write (/usr/lib/node_modules/netlify-cli/node_modules/decompress-tar/node_modules/readable-stream/lib/_stream_writable.js:334:11)
    at Gunzip.ondata (_stream_readable.js:713:22)

Here is my Netlify.toml file , IM developing a Hugo Theme and It would be convenient  If i can Easily Check the Live Version , but im stuck at that error.
[build]
  publish = "exampleSite/public"
  functions = "lambda"
  command = "hugo -s exampleSite --gc --minify --themesDir ../.. -b $HUGO_BASEURL"

[dev]
command = "hugo server mod graph --themesDir=../.. -s exampleSite"
targetPort = 1313
framework = "#custom"
port = 3000

[build.environment]
  HUGO_VERSION = "0.69.0"
  HUGO_BASEURL = "https://hugo-theme-twal-starter.netlify.app"
  HUGO_THEME = "repo"
  HUGO_ENVIRONMENT = "production"
  HUGO_ENABLEGITINFO = "true"

[context.split1]
  command = "hugo -s exampleSite --gc --minify --themesDir ../.. -b $HUGO_BASEURL --enableGitInfo"

[context.split1.environment]
  HUGO_VERSION = "0.70.0"
  HUGO_ENV = "production"

[context.deploy-preview]
  command = "hugo -s exampleSite --gc --minify --themesDir ../.. -b $HUGO_BASEURL --buildFuture"

[context.deploy-preview.environment]
  HUGO_VERSION = "0.70.0"

[context.branch-deploy]
  command = "hugo -s exampleSite --gc --minify --themesDir ../.. -b $DEPLOY_PRIME_URL"

[context.branch-deploy.environment]
  HUGO_VERSION = "0.70.0"

[context.next.environment]
  HUGO_ENABLEGITINFO = "true"

Also get this error using Gatsby

I can confirm that this error is only present when you are developing a non standard hugo site...
since I am using the theme itself as the site  , this produce this error.
but if i do use a standard Hugo site and the theme is on the theme folder i dont get it.
I think it would be useful if even in theme site we can use  --live

I dont know how i fixed this error but , i can use netlify dev --live now without any problem...

things ive change on my netlify.toml
// this command is certainly my fault wrong command
command = "hugo server mod graph --themesDir=../.. -s exampleSite"
// change to
command = "hugo server -s exampleSite --themesDir=../.. --disableFastRender"

also update my hugo version to latest 0.72.0
and added template.environment
[template.environment]
  HUGO_BASEURL = "add your custom domain name url with https protocol"
  PAYMONGO_EMAIL = "type here your paymongo username/email"
  PAYMONGO_PASS = "type here your paymongo password"
  SES_ACCESS_KEY = "type here your AWS SES Access Key"
  SES_SECREKT_KEY = "type here your AWS SES Secret Key"

but now everything i working ok

Glad it worked out for you @goldcoders


Integrate subscriptions

Related to https://github.com/CartoDB/cartoframes/issues/1079, https://github.com/CartoDB/cartoframes/pull/1087

[x] Remove do_datasets module
[x] Implement do_subscriptions module
[x] Implement do_subscription_info module

NOTE: subscriptions endpoints are WIP

Acceptance 🍏


[BUG] VideoUnavailable is raised when trailer is present and chat is disabled.

Basic information

Program version: 0.1.10
Python version: 3.10.2
Operating system: Arch Linux x64, linux 5.15.25-1-lts

Describe the bug
VideoUnavailable is raised when trailer is present and chat is disabled. Affects both cli and python api.
Command/Code used
If running from the command line, provide the following:

The command used (including the verbose tag, -v):

$ chat_downloader "yGJ6jYRfqTk" --message_groups "all" --indent 2 --log=debug

Output from the above command:

[DEBUG] Python version: 3.10.2 (main, Jan 15 2022, 19:56:27) [GCC 11.1.0]
[DEBUG] Program version: 0.1.10
[DEBUG] Initialisation parameters: {'headers': None, 'cookies': None, 'proxy': None}
[DEBUG] Created YouTubeChatDownloader session.
[INFO] Site: youtube.com
[DEBUG] Program parameters: {'url': 'yGJ6jYRfqTk', 'start_time': None, 'end_time': None, 'max_attempts': 15, 'retry_timeout': None, 'interruptible_retry': True, 'timeout': None, 'inactivity_timeout': None, 'max_messages': None, 'message_groups': ['all'], 'message_types': None, 'output': None, 'overwrite': True, 'sort_keys': True, 'indent': 2, 'format': 'youtube', 'format_file': None, 'chat_type': 'live', 'ignore': None, 'message_receive_timeout': 0.1, 'buffer_size': 4096}
[DEBUG] Starting new HTTPS connection (1): www.youtube.com:443
[DEBUG] https://www.youtube.com:443 "GET /watch?v=yGJ6jYRfqTk HTTP/1.1" 200 None
<too long, see response in file>
[ERROR] LIVE_STREAM_OFFLINE: This live event will begin in 15 hours.
[DEBUG] Session closed.

If the output is too long, you can attach a text file or remove output which does not constitute to the problem.
Expected behavior
ChatDisabled should be raised.
Additional context/information
VideoUnavailable tells us that the video is removed, while ChatDisabled tells us to retry.
In the player response, the playabilityStatus has the "errorScreen" key pair containing an embedded trailer which causes chat_downloader to assume an error, even though the status is simply LIVE_STREAM_OFFLINE.
  "errorScreen": {
     "ypcTrailerRenderer": {
      "fullVideoMessage": {
       "simpleText": "Trailer"
      },
      <embedded player response here>
  ...

response

Sure, I can fix that 👍
Do you have another example of a video I can test on?

This has been fixed in https://github.com/xenova/chat-downloader/commit/50b8ed2e32f098840b86ecb7c0518f9c101ba50f


a plugin manager to maintain and configure your oh-my-zsh installation

This is a plugin for oh-my-zsh
With that plugin you can

list_plugins
enable_plugin
disable_plugin
download_and_enable_plugin
list_themes
enable_theme
download_and_enable_theme
update_plugin
update_theme

I agree with @mcornella, @robbyrussell or @mbauhardt please close for now.


Feature: Make JWT tokens stateful even for Users / Apps - add this as a selectable option

Is your feature request related to a problem? Please describe.
Current JWT are stateless (which makes sense in many applications for the sake of efficiency and philosophy behind JWTs), but it would be good to have a stateful option as well
Describe the feature you are requesting, as well as the possible use case(s) for it.
For some applications it is important that session is controlled, stopped and tokens can be revoked
Indicate the importance of this feature to you.
Must-have
Anything else?
No response

There are two main methods to handle user authentication, that is session-based authentication and token-based authentication.
Session-based authentication
Session-based authentication relies on a server-side mechanism that creates and stores a unique identifier for each user session. When a user logs in, the server generates a session ID and sends it to the client as a cookie. The client then sends the cookie back with every request, and the server validates it against its session store.
Token-based authentication
Token-based authentication relies on a client-side mechanism that uses self-contained tokens to store and transmit user information. When a user logs in, the server generates a token that contains the user's identity, claims, and expiration time, and signs it with a secret key. The server then sends the token to the client, which can store it locally or in memory. The client then sends the token with every request, and the server verifies it by checking its signature and validity. This way, the server does not need to maintain a session store or state.
Differences

Key
Session
Tokens

storage
on the server
on the client

state
stateful
stateless

Expiry
handled by server
handled by token itself

flexibility

more flexible

Using JWT For Sessions
While JWT are commonly used for token-based authentication, they might not be suitable for session-based authentication due to security concerns. This article provides detailed insights into this matter.
Session Infrastructure

CREATE TABLE sessions (
	id uuid NOT NULL,
	issued_at timestamp DEFAULT CURRENT_TIMESTAMP NOT NULL,
	expires_at timestamp NOT NULL,
	authenticated_at timestamp NOT NULL,
	identity_id uuid NOT NULL,
	created_at timestamp NOT NULL,
	updated_at timestamp NOT NULL,
	access_token varchar NOT NULL,
	refresh_token varchar NOT NULL,
	active bool DEFAULT false NULL,
	device_metadata JSONB NULL,
	CONSTRAINT sessions_pkey PRIMARY KEY (id)
);

NOTE

We can consider employing Platform Agnostic Security Tokens instead of JWT for session-based authentication due to potential security risks.
Session-based authentication proves ideal for UI backend implementations, while token-based authentication serves well for communication between Magistrala core and the UI.


tests: update packages to keep ceph common and libraries in sync

Sometimes the version in the RPM repository don't match the version
of the base image. This change updates the packages before installing
the libraries in order to make them match.
Signed-off-by: Sven Anderson<EMAIL_ADDRESS>

nit in the commit message: the version in the RPM repository don't match. s/don't/doesn't

Right, but I will just leave it like that so we don't have to restart the tests. I guess you agree. ;-)


Automatic Chat Clearing

Is your feature request related to a problem? Please describe.
It is not related to a problem caused by your module, but by Foundry itself. I've created a script to automatically prune the chat log and lighten the initial load into a game.
Describe the solution you'd like
A friend of mine had the problem that the initial load took several minutes at times and the issue was caused by an excessive amount of chat messages. I though of a solution which automatically deletes messages.
Here's the code:
Hooks.once("init", function(){ 	game.settings.register('auto-clear-messages', 'delete-at-length', { 		name: 'When to clear chat messages?', 		label: 'When to clear chat messages?', 		type: Number, 		default: 1000 	}); 	game.settings.register('auto-clear-messages', 'clear-amount', { 		name: 'How many messages should be cleared?', 		label: 'How many messages should be cleared?', 		type: Number, 		default: 500 	}); 	const length = $('#chat-log').find('li.chat-message').length; 	const delAtLength = game.settings.get('auto-clear-messages', 'delete-at-length'); 	if(delAtLength !== 0){ 		const amount = game.settings.get('auto-clear-messages', 'clear-amount') 		let i = 0; 		if(length >= delAtLength){ 			game.messages.forEach(function(m){ 					if(i !== amount){ 						m.delete(); 						i++; 					}; 			}); 		}; 	}; });
I would love to see you implement this feature into your module, maybe by additionally providing a boolean to enabled/disable this feature. It would likely help a lot of people that do have the same issue that my friend had. I can also create my own module, but yours has way more bandwidth, so I think it would be suited better here.

This issue might be solved already in the latest Foundry - it only loads the last 100 messages initially, and only loads more if you scroll up to see them.
Do you still see the slowness in Foundry v11 Build 315?
I'm able to load a world with 81k chat messages without any noticeable slowness.
If you do still see the issue, which of the following solutions would you prefer?

Automatically deleting the oldest message(s) whenever a new message is created and there are more than N total messages
Replacing the "Clear Chat Log" button with a "Clean Chat Log" button that asks for the number of messages to keep instead of being "all or nothing".
Automatically deleting messages older than N days whenever a GM logs in, and every 30 minutes (until the GM logs out or closes their browser)
Replacing the "Clear Chat Log" button with a "Clean Chat Log" button that asks for a date, and deletes all chat messages before that date
Replacing the "Clear Chat Log" button with a "Clean Chat Log" button that asks for a date and time, and deletes all chat messages before that date-time

The Error occured with the newest stable Foundry Release (11.315). I still don't know why it only happened for my friend, but after pruning the 116K messages the Game loaded for him lickety-split.
I'd say three settings should be present for this:

a bool to select If the chat should be automatically cleaned
Message trigger amount (eg. 1000) as a Number
Message clear target (eg. 500) as a Number (how many messages should be left after clearing)
(optional) bool to Archive the messages with the current Date instead of only deleting

The check should be made on an Initial load for the GM.
You could also add a dropdown with different settings for the Message clear options an include more of the options you've suggested.
Thanks for looking into this ♥


Where i can get Hardware Security Test Interface

How do i test  my hardware as in laptop   for  security  purpose , i am end user

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

ID: 29c9d886-f326-ddca-309d-fde727ab0289
Version Independent ID: 5be6b02c-bff3-5af3-5afa-ea92890afd30
Content: Hardware Security Test Interface (HSTI) 1.1a - Windows drivers
Content Source: windows-driver-docs-pr/bringup/hardware-security-test-interface-1-1a.md
Product: windows-hardware
GitHub Login: @barrygolden
Microsoft Alias: bagold

Thanks for reaching out to the Windows Driver Developer Documentation team.
You may have success posting your question in the following forums, where other driver developers and Microsoft engineers can be found. The community there is quite responsive.
MSDN Windows Hardware WDK and Driver Development forum
NTDEV forum at OSR Online


Company Fees Contract Page - Required option to send contract to multiple client By Vinod Sir

Describe the bug

When we select multiple company then there should be option for send them contract

https://www.berrycast.com/conversations/f1d42c2b-d157-56ba-98f3-70a0f60cdc75

#1609
Duplicate


RUM-3280 Remove spotbugs and slf4j dependencies in the dd-trace-core module

What does this PR do?
In this PR we are doing more cleanup work in the dd-core-tracer java module:

removing the slf4j dependency and switching to a NoOpLogger internally for now. A task was added to JIRA to add a proper logger implementation later
removing the spotbug dependency which solved the last lint rule in the project
making sure the compiler does not complain in the integration test project due to the opentelemetry API using the  Google autovalue annotations

Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #1901 (d342738) into feature/otel-support (3748b40) will increase coverage by 0.10%.
The diff coverage is n/a.

Additional details and impacted files
@@                   Coverage Diff                    @@
##           feature/otel-support    #1901      +/-   ##
========================================================
+ Coverage                 82.34%   82.44%   +0.10%
========================================================
  Files                       481      481
  Lines                     17020    17031      +11
  Branches                   2580     2580
========================================================
+ Hits                      14014    14040      +26
+ Misses                     2299     2284      -15
  Partials                    707      707

see 26 files with indirect coverage changes


fix: remove duplicate tailwind classes in RequestNotFound component

Description
I'm just removing classes that are duplicated in the RequestNotFound component.
Contribution Checklist:

[x] The pull request only addresses one issue or adds one feature.
[x] The pull request does not introduce any breaking changes
[ ] I have added screenshots or gifs to help explain the change if applicable.
[x] I have read the contribution guidelines.
[ ] Create an issue and link to the pull request.

Merged! Thanks @dan1xk !


Migrating from agencyenterprise/react-native-health

This is not really an issue, just a thread for those who are looking to move away from agencyenterprise/react-native-health.
I was looking for an alternative that doesn't hide functionality, uses non-deprecated solutions and comes with proper type definition. Even though this package doesn't have extensive documentation I think it's still a pretty good alternative. (Also, It's in swift which is a bonus over objc)
I've spent some time on creating a simple 1-way workout sync and I ended up using the following snippet:
import HealthKit, {
  HKQuantityTypeIdentifier,
  HKWorkoutActivityType,
  HKWorkoutTypeIdentifier,
} from '@kingstinct/react-native-healthkit';
import { v4 as uuid } from 'uuid';

const main = async () => {
  const isAuthed = await HealthKit.requestAuthorization(
    [HKWorkoutTypeIdentifier, HKQuantityTypeIdentifier.activeEnergyBurned],
    [HKWorkoutTypeIdentifier, HKQuantityTypeIdentifier.activeEnergyBurned],
  );

  if (!isAuthed) {
    return -1;
  }

  // This data comes from our API
  const externalId = uuid();
  const startDate = new Date('2022-01-01T00:00:00.000Z');
  const endDate = new Date('2022-01-01T00:13:00.000Z');

  await HealthKit.saveWorkoutSample(
    HKWorkoutActivityType.highIntensityIntervalTraining,
    [
      {
        quantityType: HKQuantityTypeIdentifier.activeEnergyBurned,
        unit: 'kcal',
        quantity: 666,
      },
    ],
    startDate,
    {
      end: endDate,
      metadata: {
        HKExternalUUID: externalId,
      },
    },
  );
}

Glad you find it useful!
Feel free to PR improvements on the documentation side :)


Fix simultaneous homalt and het genotyping issue arising due to multi-allelic splitting followed by hotfix for depletion of homozygous alternate genotypes

See full thread discussion here: https://atgu.slack.com/archives/CNNTF8Z46/p1620401614102100
Summary of problem written up by KC:
there is a problem with our code fix correcting the depletion of homozygous alternate genotypes (the fix is described in this blog post). in certain situations, samples that have heterozygous alternate calls at multiallelic sites may end up having both a heterozygous and a homozygous genotype at a locus after splitting multiallelics.
here’s an example (found in the 455k ukbb tranche):
chr22:19233125 has a reference allele of G and alternate alleles of A, C, GTGTGGT, and T. a sample at this site has an A/T genotype. after splitting multiallelics, we would expect that the genotypes for this sample would look like this:
chr22:19233125 G>A 0/1
chr22:19233125 G>C 0/0
chr22:19233125 G>GTGTGGT 0/0
chr22:19233125 G>T  0/1
however, it turns out that our code fix changes het genotypes with high allele balances at chr22:19233125 G>A to be homozygous alternate. thus, the genotypes for this sample actually look like this:
chr22:19233125 G>A 1/1
chr22:19233125 G>C 0/0
chr22:19233125 G>GTGTGGT 0/0
chr22:19233125 G>T 0/1
so you can see that with the code fix, this sample has both a homalt and a het call at this locus

should be fixed by the following PRs and can close this when they go in:  #205 #206

Closing because this has been fixed in the code and there are other tickets referring to the actual gnomAD fix


fix: add a missing experimental template to C3 for asset-only Worker

What this PR solves / how to test
Fixes N/A
Author has addressed the following

Tests

[ ] TODO (before merge)
[ ] Tests included
[x] Tests not necessary because: experimental C3 template

E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)

[ ] I don't know
[ ] Required
[x] Not required because: experimental C3 template

Changeset (Changeset guidelines)

[ ] TODO (before merge)
[x] Changeset included
[ ] Changeset not necessary because:

Public documentation

[ ] TODO (before merge)
[ ] Cloudflare docs PR(s):
[x] Documentation not necessary because: experimental C3 template

Oops sorry @edmundhung - I merged it before I saw your review. I'll follow up now with another PR.


EuroScipy 2016

https://www.euroscipy.org/2016/

In previous years it was published here: https://www.youtube.com/user/EnthoughtMedia/playlists


Getting buildah commit docker-formatted images to local docker storage

Apologies if I've overlooked something or (more likely) have a shaky understanding of the different formats, transports and storage locations.
Is there a way to get buildah-made, docker-formatted images (ie: buildah commit -f docker $container my_image) from buildah image storage to storage available for use by the docker daemon without pushing to a remote registry?
I am unclear on when to use buildah commit vs. buildah export, and how to move those images to other places.
I also investigated skopeo as a potential solution, but was unsure how to (or if I could) reference buildah images using the transports that skopeo uses.
Any guidance is appreciated, thanks!

Does
buildah push my_image
Work?

Hi @rhatdan:
buildah push my_image
ERRO[0000] source and destination image IDs must be specified

I would have thought that would work too.  The man page and --help output have destination as an optional parameter (or in brackets anyway).
So I tried a few variants with a destination image.
buildah push my_image my_image
ERRO[0000] Invalid image name "my_image", expected colon-separated transport:reference

I'm not clear on how to reference the local docker storage on my laptop in the transport.  I tried a few variations, with different messages:
buildah push my_image docker://my_image
Getting image source signatures
ERRO[0023] error pushing image "my_image" to "docker://my_image": error copying layers and metadata: Error checking for blob sha256:d3aeceeb0289bf97c2474366cfcdaf66e29b409d45d6ed91be3335f16915f1b0 at destination: not authorized to read from destination repository library/my_image

buildah push my_image docker://localhost/my_image:latest
Getting image source signatures
ERRO[0022] error pushing image "my_image" to "docker://localhost/my_image:latest": error copying layers and metadata: Error checking for blob sha256:d3aeceeb0289bf97c2474366cfcdaf66e29b409d45d6ed91be3335f16915f1b0 at destination: pinging docker registry returned: Get https://localhost/v2/: dial tcp [::1]:443: getsockopt: connection refused

The last makes sense, I guess.  I'm not listening via TCP on my own laptop.  Is there a way to push to the local storage by file, or to the daemon by socket?  Or is it intended to be used via TCP and the Docker REST api?
Am I just using the wrong transport for what I'm trying to do?
Thanks for your help!

The docker:// transport talks to registries.  You should have success using docker-daemon:image-name:tag as a destination, though.

@nalind: That worked perfectly!  I had not known the docker-daemon transport existed.
Thanks for the assistance, all!

That's a good point - we don't list it as an example in the buildah-push(1) man page, and there isn't much else describing where we can write images.

Yes we should add it to the man page.  Also we should add it to help.  I was talking to @14rycole about this point.  BTW Can you do some of this in buildah commit?

Yeah, commit can still write to any of the locations to which push can write.


SSB: Protect blocks Soup Stealing 7 star strike

Why are these all attrLastMove('[still]') instead of attrLastMove('[anim]')?

Thats how it was in Joim's SSB and I never bothered to look into if there was a better way since it was working.


Display/Frame text components should not use font fallback

We don't need font fallback for display/frame, b/c validity of the out beats the expediency in that case. Otherwise currently in most of cases switching a font has multiple jumps in the display canvas.
/cc @barklund

As a further potential improvement, we can also look into font-display for the fonts. Though I don't think we use at-font-face there.

Notice, this is related but not exactly the same as #1008. But they can share some infrastructure.

@dvoytenko, is the intent to force gfonts to use font-display: block while in-editor (but use fallback in client-side AMP story) and remove fallback fonts here, or?

Yes. The editor itself should prefer font-display: block. The output should prefer swap or fallback. And other features - somewhere in between. E.g. font picker menu should probably use swap. In addition this affects font-family: "my font", ...fallback....
The reasoning is this: if you change the font family in the editor in the side panel, it's pretty much always shows fallback first right now and after awhile it jumps to the right font. Thus from editing point of view, fallback is not helpful.
In terms of work being done here: some of this problem is getting resolved in @obetomuniz's #1275. I think that approach will resolve most of editing problems, but I think the display problems will still remain, and can only be solved by correct font-face and fallback CSS.

Started looking into this, however, it doesn't look like the font fallback is used anymore for display/edit, also, there is no font jumping when switching between the fonts anymore.
Looks like we might be able to close this issue.
Thoughts, @barklund ?

Verified in QA

@miina can this be moved to done & closed?


Fix issue #128 (recoverNearest for full OLC)

Description of recoverNearest claims that a valid full code will be returned unchanged. As implemented, actually raises a ValueError. Fixed by returning a valid full code properly capitalized, but otherwise unchanged.

Thanks!

delete branch after merge


No "Manage Plug-ins..." available

Using OS 11.2.2, installed MailTrackerBlocker today, but there's no such option.

The option did not show up for me, either, because I didn't actually install the plug-in, I just downloaded the package. After I installed it, the option showed up, I assume it was activated by the installation. I am on Catalina 10.15.7.
Another possibility: Did you restart Mail?

I did install it, and restarted mail. Mail was quit before installation.

Sorry, that's all I got. Someone more skilled than I will have to help.
Wait, one more idea in passing: how abut rebooting the Mac? Just a guess, though

OK, just one more idea... I had to install it twice to get it to show up correctly.

Alas, no. Rebooted and reinstalled.  I suspect, instead, it's something basic.  Like: Is it supposed to just drop in a file somewhere?  Because I can't find it.  I just created a new folder, where there was none, at (user)/Library/Application Support/Mail/Plug-ins.

The installer will put the various pieces where they belong. None of which go in /Mail/Plug-ins.
The first time I downloaded the file to the desktop then double-clicked on that, but that didn’t do a complete job of installing so I tried again. What worked best for me was to go to the website, click the download icon, then just let the Installer do its work.
On Mar 2, 2021, 11:48 AM -0800, markles2<EMAIL_ADDRESS>wrote:

Alas, no. Rebooted and reinstalled. I suspect, instead, it's something basic. Like: Is it supposed to just drop in a file somewhere? Because I can't find it. I just created a new folder, where there was none, at (user)/Library/Application Support/Mail/Plug-ins.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

The option did not show up for me, either, because I didn't actually install the plug-in, I just downloaded the package. After I installed it, the option showed up, I assume it was activated by the installation. I am on Catalina 10.15.7.
Another possibility: Did you restart Mail?

MailTrackerBlocker doesn't work in macOS 10.11 or higher because at least through 10.13.6, there has never been a Manage Plug--ins option in the General preferences section. That's only been there in the most recent versions of macOS. MailTrackerBlocker isn't a plug-in either: it's a Mail Bundle that should appear separately in Mail Preferences like other bundles, but it doesn't.
I don't think the author of this has tested it in macOS 10.11 or higher; just the most recent version.

Ah! That explains it.  Thanks.

@Mulder-X1 I usually test on 10.14, 10.15 and 11.2
@markles2 The "Manage Plug-ins" button is normally hidden by default. My installation pkg is supposed enable this but apparently it hasn't been working for a lot of people.
Could you let me know what the output of this is?
sudo defaults read "/Library/Preferences/com.apple.mail" EnableBundles
defaults read com.apple.mail EnableBundles
defaults read com.apple.mail BundleCompatibilityVersion

On Mar 2, 2021, at 7:57 PM, Aaron Lee<EMAIL_ADDRESS>wrote:
@Mulder-X1 https://github.com/Mulder-X1 I usually test on 10.14, 10.15 and 11.2
@markles2 https://github.com/markles2 The "Manage Plug-ins" button is normally hidden by default. My installation pkg is supposed enable this but apparently it hasn't been working for a lot of people.
Could you let me know what the output of this is?
sudo defaults read "/Library/Preferences/com.apple.mail” EnableBundles
1
defaults read com.apple.mail EnableBundles
YES
defaults read com.apple.mail BundleCompatibilityVersion
The domain/default pair of (/Users/Mulder/Library/Containers/com.apple.mail/Data/Library/Preferences/com.apple.mail, BundleCompatibilityVersion) does not exist
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/apparition47/MailTrackerBlocker/issues/50#issuecomment-789365257, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATB6BXQDOXTRRSXURLZAWDTTBWJP5ANCNFSM4YPMJHZQ.

@Mulder-X1 Are you having the same issue as @markles2 ?

Yes, I'm having the same issue, there's no Manage Plug-ins option available. I'm running 10.13.6
Thanks, Mark

Basically similar results as Multer-X1:
1
1
… does not exist.
I wonder if that last one, the non-existence of the folder/file is the problem.
FYI I'm running OS 11.2.2 (Big Sur)

I wonder if that last one, the non-existence of the folder/file is the problem.

Apparently not since I have the exact same output as @Mulder-X1 .
sudo defaults write "/Library/Preferences/com.apple.mail" EnableBundles 1
defaults write com.apple.mail EnableBundles -bool true

These commands (which are executed by the installer) are supposed to enable Manage Plug-ins... but for whatever reason, it's not working on your setups. Still investigating.

ℹ (EDIT: 0.3.16 has been released. Let's work with that as a baseline.)

I wonder if that last one, the non-existence of the folder/file is the problem.

Apparently not since I have the exact same output as @Mulder-X1 .
These commands (which are executed by the installer) are supposed to enable Manage Plug-ins.... Maybe try give it a try:
sudo defaults write "/Library/Preferences/com.apple.mail" EnableBundles 1
defaults write com.apple.mail EnableBundles -bool true
defaults write com.apple.mail BundleCompatibilityVersion 4

Yes, I am. I’m running macOS 10.13.6 and I’ve tried installing it via the package, and via Homebrew and t he result is the same. But currently, in 10.13.6 V5 is the current version for bundle compatibility.

On Mar 2, 2021, at 11:49 PM, Aaron Lee<EMAIL_ADDRESS>wrote:
@Mulder-X1 https://github.com/Mulder-X1 Are you having the same issue as @markles2 https://github.com/markles2 ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/apparition47/MailTrackerBlocker/issues/50#issuecomment-789453758, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATB6BXXDJA7AB4RDKKNDMP3TBXEXVANCNFSM4YPMJHZQ.

FWIW, I get the same results as Markles2 (1, 1, does not exist) yet my installation is working fine. Catalina 10.15.7.

Additional result...In High Sierra, ran installation and got no "Manage Plug-ins" in Mail preferences, but the "x" button is working fine and identifying trackers.

Read about MailTrackerBlocker at Daring Fireball; sounded good, so I downloaded it. Running macOS 10.12.6 Sierra on my MacBook Pro 10,1. I ran the Installer, it seemed to work okay. Opened Mail, but there was no [Manage Plug-Ins] button at the bottom of Preferences > General as pictured. Did a search and found it had been installed: /Library/Mail/Bundles/MailTrackerBlocker.mailbundle.
So went to my other MacBook Pro (11,4), started in Sierra, did the same there, same result: bundle installed, but no way to activate it. Started in Catalina, opened Mail, saw no [Manage Plug-Ins] button at the bottom of Preferences > General, but there was space in the window for something. So installed MailTrackerBlocker, and now the [Manage Plug-Ins] button appeared. Did a search, found MailTrackerBlocker.mailbundle installed as in Sierra. So it works in Catalina, though the button doesn't show unless a Plug-In is installed. But it doesn't seem to work in Sierra.
Tried the three Terminal commands above in Sierra, still no [Manage Plug-Ins] button in Mail Preferences, but now there's space for it in the bottom of the window, where before the "Encrypted Messages" checkbox line was right down at the bottom of the window.
And the little X button now appears with each message opened in Mail. So it's working, even without being enabled.
So just for grins, since the download button says "macOS 10.11+", I tried it in 10.11.6 El Capitan on my MacBook. But the Installer balked: "MailTrackerBlocker.pkg can't be installed because its digital signature is invalid. The package may have been corrupted or tampered with. Get a new copy of the package and try again."
So I went to the Web page and downloaded it again. Same result. So it seems it can't be installed in 10.11.
Anyway, thought you'd like to know.

@ronewby @OofyProsser @HandyMac For those who are reporting it working without manually enabling it after installation, do you have SIP disabled?

So it seems it can't be installed in 10.11.

Addressed in #53.

SIP is enabled.

On Mar 4, 2021, at 9:49 PM, Aaron Lee<EMAIL_ADDRESS>wrote:
@ronewby https://github.com/ronewby @OofyProsser https://github.com/OofyProsser @HandyMac https://github.com/HandyMac For those who are reporting it working without manually enabling it after installation, do you have SIP disabled?
So it seems it can't be installed in 10.11.
Addressed in #53 https://github.com/apparition47/MailTrackerBlocker/issues/53.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/apparition47/MailTrackerBlocker/issues/50#issuecomment-791151326, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATCNKQMS63X4JVELQSK3XD3TCBPG5ANCNFSM4YPMJHZQ.

Managed to provision a 10.13.6 system. Just to confirm what @Mulder-X1 said, MailTrackerBlocker will be automatically enabled on 10.13 and older. Just look for the ⓧ icon to double check. I'll clarify this in the docs.
Still not sure why "Manage Plugins" isn't showing for certain Big Sur users like @markles2 yet. Still investigating this case.

@ronewby @OofyProsser @HandyMac For those who are reporting it working without manually enabling it after installation, do you have SIP disabled?

SIP is not disabled; didn't even think of it.

MailTrackerBlocker will be automatically enabled on 10.13 and older. Just look for the ⓧ icon to double check.

Yes. Just tried in 10.12 Sierra again (another setup where it hadn't been installed before). After running the installer, the ⓧ is present in Mail's message window, though the [Manage Plug-Ins] button does not appear in Mail's Preferences. Tried the three Terminal commands, one at a time, but the [Manage Plug-Ins] button did not appear.  Went back to the two Sierra setups where I'd installed MailTrackerBlocker last night; there is now no extra space in the Mail Preferences window in either (don't remember in which one that happened).

MailTrackerBlocker isn’t configured on my10.13.6 system. Doesn’t matter if SIP is enabled or disabled — the result is still the same.

On Mar 5, 2021, at 12:07 AM, Aaron Lee<EMAIL_ADDRESS>wrote:
Managed to provision a 10.13.6 system. Just to confirm what @Mulder-X1 https://github.com/Mulder-X1 said, MailTrackerBlocker will be automatically enabled on 10.13 and older. Just look for the ⓧ icon to double check. I'll clarify this in the docs.
Still not sure why "Manage Plugins" isn't showing for certain Big Sur users like @markles2 https://github.com/markles2 yet. Still investigating this case.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/apparition47/MailTrackerBlocker/issues/50#issuecomment-791180881, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATB6BXUM6XZISICDFPOGICLTCBYJBANCNFSM4YPMJHZQ.

@HandyMac If you're seeing the ⓧ icon in the Mail message window beside the subject line and under the date, then you're ready to go.

MailTrackerBlocker isn’t configured on my10.13.6 system. Doesn’t matter if SIP is enabled or disabled — the result is still the same.

SIP doesn't matter; it doesn't prevent installing MailTrackerBlocker. Go to /Library/Mail/Bundles/: is MailTrackerBlocker.mailbundle there? If it is, it should be working. If not, run the Installer again.
Open a message in Mail, look to the right; the ⓧ is small and unobtrusive. Here it is in my 10.13.6 Mail:

MailTrackerBlocker is definitely installed, and now that I know what to look for, I see a small blue ⓧ on the far right of a message, underneath the time of arrival. Still nothing in Mail preferences.

On Mar 5, 2021, at 9:43 AM, HandyMac<EMAIL_ADDRESS>wrote:
MailTrackerBlocker isn’t configured on my10.13.6 system. Doesn’t matter if SIP is enabled or disabled — the result is still the same.
SIP doesn't matter; it doesn't prevent installing MailTrackerBlocker. Go to /Library/Mail/Bundles/: is MailTrackerBlocker.mailbundle there? If it is, it should be working. If not, run the Installer again.
Open a message in Mail, look to the right; the ⓧ is small and unobtrusive. Here it is in my 10.13.6 Mail:
https://user-images.githubusercontent.com/31111465/110138003-ba56a280-7d8e-11eb-9d29-c1b402542f7f.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/apparition47/MailTrackerBlocker/issues/50#issuecomment-791500309, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATB6BXXXHGJ6ZDZIJIPP4GLTCD3ZDANCNFSM4YPMJHZQ.

I don’t recall seeing this mentioned, so I will point it out just in case anyone else missed it, too:
If you click on the blue ⓧ, MTB will tell you how many trackers were blocked and who they were from. The white ⓧ indicates that MTB did not find anything to block.
Jerry

@Mulder-X1 @OofyProsser Trying to keep the plugin unobtrusive so that's probably why you missed missed it. Others were confused about how it works too (#33). Probably reinforces the need for better documentation. Anyway, sounds like the issue is solved in your cases.
@markles2 Since you're running Big Sur, you should be the one to see "Manage Plug-ins". Are you still having this issue on 0.3.17?

No.  I still do not see (or have?) the "Manage Plug-ins" option in Mail>Preferences>General after having installed 0.3.17 over Mac OS 11.2.2 ("Big Sur").

Which is the latest version of MailTrackerBlocker? I thought I would install it in Big Sur, to provide you more than one example. So I downloaded it fresh from the Web page. And found one I'd downloaded earlier today is actually a "later" version. The one I just downloaded is 127,427 bytes, Created March 6, 2021 at 6:02 PM, Modified March 6, 2021 at 6:02 PM. (These two times seem to be when I downloaded it just now here in MST.) The one I downloaded this morning from one of your links is 127,471 bytes, Created March 6, 2021 at 5:28 AM, Modified March 6, 2021 at 9:10 PM. (How it could have been modified ~3 hours in the future (from now) is a mystery to me.) Which one should I install in Big Sur?

Modification times (and date) are designated to be the time you downloaded the item, not the actual time it was created or modified by the developer.

On Mar 6, 2021, at 7:14 PM, HandyMac<EMAIL_ADDRESS>wrote:
Which is the latest version of MailTrackerBlocker? I thought I would install it in Big Sur, to provide you more than one example. So I downloaded it fresh from the Web page. And found one I'd downloaded earlier today is actually a "later" version. The one I just downloaded is 127,427 bytes, Created March 6, 2021 at 6:02 PM, Modified March 6, 2021 at 6:02 PM. (These two times seem to be when I downloaded it just now here in MST.) The one I downloaded this morning from one of your links is 127,471 bytes, Created March 6, 2021 at 5:28 AM, Modified March 6, 2021 at 9:10 PM. (How it could have been modified ~3 hours in the future (from now) is a mystery to me.) Which one should I install in Big Sur?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/apparition47/MailTrackerBlocker/issues/50#issuecomment-792142047, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATB6BXUZ7MEEX3FJQ6A2LSTTCLHO5ANCNFSM4YPMJHZQ.

Closing this issue. Still not sure why "Manage Plug-ins..." isn't showing up for @markles2 on Big Sur and as of 0.3.22, it shouldn't really be an issue anyway due to the Big Sur auto-enabler script I setup on install.


Fix blank options in 'Select A Topic' drop-down in mobile browsers

- Summary
Fixes #1088.
Topics with a blank title are rendered as an option without any text.
- Description for the changelog
Filter out topics with a blank title.

Deploy preview for cms-demo ready!
Built with commit cd12e16e029479223d2fd7ba937a5daea0703170
https://deploy-preview-1124--cms-demo.netlify.com

Deploy preview for netlify-cms-www ready!
Built with commit cd12e16e029479223d2fd7ba937a5daea0703170
https://deploy-preview-1124--netlify-cms-www.netlify.com


feat: Add catchuptvandmore and dependencies

Description of changes
Hello :wave: ,
I've been working on packaging Catchup TV And More for Kodi and all it's dependencies. I've made some progress but I'm looking for some help/guidance.

First of all, I've seen some Kodi packages having:

  passthru = {
    pythonPath = "lib";
    updateScript = addonUpdateScript {
      attrPath = "kodi.packages.arrow";
    };
  };

but not all of them. I couldn't find any documentation (In both Nixpkgs or Kodi wiki): when is passthru needs to be used (for either pythonPath or updateScript?

Catchup TV And More gets installed on Kodi but fails on launch, I couldn't find anything in ~/.kodi/temp/kodi.log, is there a good way to debug this?

So far, the only meaningful information I found was looking at the dependencies list in Kodi, where some of the dependencies I packaged are correctly picked-up, while some others are considered not available.

Thank you for any help you might provide,
Notifications
Kodi maintainers (let me know if it's not the right way to ask for review :pray: ):
@aanderse
@cpages
@edwtjo
@minijackson
@peterhoeg
@sephalon
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

i'll address your questions a bit later, just heading out now... almost got it to work, remaining issue is error <general>: Add-on 'script.module.pytz' is not compatible with Kodi
take a look at my fixups if you want to keep hacking on this in the meantime

i pushed a couple more fixes so the addon will actually run now
i had success playing some videos, but failures trying to play many more
some failures were errors in the streams, some failures seemed to be out of date code, and others i didn't understand what was wrong
example: AttributeError: module 'kodi_six.xbmc' has no attribute 'translatePath'
i suggest you pull my commit into your branch and try the application... see how it goes
let me know if you need any more help

passthru.updateScript is documented here
passthru.pythonPath is a specific to kodi.packages packages and "documented" here... better documentation wasn't much of a priority for me because not many people were contributing to kodi up until recently

if you take a look at:

the "documentation" i linked above
the source code of the dependencies you packaged
the pythonPath that i set for the dependencies you packaged

i think you will understand very clearly what pythonPath is for... though if you don't please let me know and i can try to improve upon the explanation

Thanks a lot for both your fixups and your explanations/documentation! This helped a lot. I was able to fix a few things I just pushed.
I'm still encountering an issue with some videos: the addon downloads the ChromeOS image to extract WidevineCDM  to read some contents, which fails:
2023-10-24 10:43:34.367 T:7322  warning <general>: [script.module.inputstreamhelper] Recursively create directory '/home/kodi/.kodi/userdata/addon_data/script.module.inputstreamhelper/backup/'.
2023-10-24 10:43:37.517 T:7322  warning <general>: [script.module.inputstreamhelper] Downloading ChromeOS image for Widevine: trogdor (15572.63.0)
2023-10-24 10:43:37.918 T:1833     info <general>: Loading skin file: DialogConfirm.xml, load type: KEEP_IN_MEMORY
2023-10-24 10:48:18.273 T:7322  warning <general>: [script.module.inputstreamhelper] Recursively create directory '/home/kodi/.kodi/userdata/addon_data/script.module.inputstreamhelper/backup/15572.63.0/'.
2023-10-24 10:48:18.356 T:7322  warning <general>: [script.module.inputstreamhelper] Recursively create directory '/home/kodi/.kodi/cdm/'.
2023-10-24 10:48:18.357 T:7322  warning <general>: [script.module.inputstreamhelper] Hardlink file '/home/kodi/.kodi/userdata/addon_data/script.module.inputstreamhelper/backup/15572.63.0/config.json' to '/home/kodi/.kodi/cdm/config.json'.
2023-10-24 10:48:18.360 T:7322  warning <general>: [script.module.inputstreamhelper] Hardlink file '/home/kodi/.kodi/userdata/addon_data/script.module.inputstreamhelper/backup/15572.63.0/libwidevinecdm.so' to '/home/kodi/.kodi/cdm/libwidevinecdm.so'.
2023-10-24 10:48:18.363 T:7322  warning <general>: [script.module.inputstreamhelper] Hardlink file '/home/kodi/.kodi/userdata/addon_data/script.module.inputstreamhelper/backup/15572.63.0/recovery.json' to '/home/kodi/.kodi/cdm/recovery.json'.
2023-10-24 10:48:18.430 T:7322  critical <general>: [script.module.inputstreamhelper] ['ldd', '/home/kodi/.kodi/cdm/libwidevinecdm.so'] cmd failed.
2023-10-24 10:48:18.431 T:7322  critical <general>: [script.module.inputstreamhelper] Failed to check for missing Widevine libraries.
2023-10-24 10:48:18.901 T:1997     info <general>: CActiveAESink::OpenSink - initialize sink

So I've tried manually running the command that fails:
$ ldd /home/kodi/.kodi/cdm/libwidevinecdm.so
/home/kodi/.kodi/cdm/libwidevinecdm.so: error while loading shared libraries: /home/kodi/.kodi/cdm/libwidevinecdm.so: DT_RELR without GLIBC_ABI_DT_RELR dependency

I'm not quite sure how to fix this issue unfortunately. I'll try to take some time to look into it but any idea is welcome.

i think i used widevine a number of times in the past without issue
a few years ago i was using the netflix addon which i am sure uses it and that was fine
i also got prompted to install widevine and i don't recall seeing those errors
i'll take another look

Thanks a lot, I tried investigating the issue but apart from the error mentionned above, I was not able to find the culprit.

errors encountered:

Error Contents: module 'kodi_six.xbmc' has no attribute 'translatePath' - looks like the addon needs updating perhaps?
2023-10-29 11:05:39.290 T:1259724   error <general>: GetDirectory - Error getting plugin://plugin.video.catchuptvandmore/resources/lib/channels/ch/srgssr/list_sub_categories/?_pickle_=8004956f000000000000007d94288c075f7469746c655f948c06436f6d656479948c076974656d5f6964948c03737266948c0c63617465676f72795f75726e948c3575726e3a7372663a746f7069633a74763a65353230383066632d663336622d343831652d393535662d30373162366338643664633394752e looks to me like the menu structure doesn't match the website... so again an issue with the addon
2023-10-29 11:09:58.479 T:1265861   error <general>: [Catch-up-TV-&-More.support] list indices must be integers or slices, not str - definitely an issue with the addon
2023-10-29 11:11:07.540 T:1266868   error <general>: [Catch-up-TV-&-More.support] 'in <string>' requires string as left operand, not NoneType - addon
2023-10-29 11:11:47.471 T:1267475   error <general>: [Catch-up-TV-&-More.support] 'url' - addon
2023-10-29 11:13:10.962 T:1270956   error <general>: [Catch-up-TV-&-More.support] ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) - looks to be that the video might not be available, or just a connection issue with the provider

i was able to start a bunch of videos from a number of countries, though i ran into a ton of issues... all of which seemed to be from the addon itself
i did not run into any widevine issue at all :man_shrugging:
have you ever used this addon before? it doesn't seem well maintained...

@M-Gregoire are you still working on this?

Hey @aanderse ,
I'm sorry for the slow reply, I haven't had much time to look into it and decided to move my Kodi host to Raspbian as I use my plugins and won't have time to migrate all of them to NixOS.
My PR was mostly working but some channels were not working.

no problem
i am sorry what we have in nixpkgs didn't suit your needs 😞 unfortunately packaging nontrivial addons can be a task sometimes
i will close this PR and in the future if anyone wants to take it over they can open a new one
best wishes


Date-filter (since, until) not working?

Hey,
I made some little tests with your great tool to get Facebook-Events by a specific location and it's working quite good. But I have problems when trying to perform a time filter on the events with the since and until parameters. For example I've tried to filter events between 2016-09-14 22:00:00 UTC and 2016-09-30 22:00:00 UTC with the queries below. First I tried with Unix-Timestamp for the since and until paramter and then with a Date-String.
http://localhost:3000/events?lat={myLatValue}&lng={myLngValue}&since=1473890400&until=1475272800&distance=10000&sort=venue&access_token={myAccessToken}
http://localhost:3000/events?lat={myLatValue}&lng={myLngValue}&since=2016-09-14T22:00:00+00:00&until=2016-09-30T22:00:00+00:00&distance=10000&sort=venue&access_token={myAccessToken}
With each of these both request for example the second event in the received event list has ["eventStarttime"]=> string(24) "2016-09-11T13:00:00+0200", which doesn't match the filter. Can you reproduce this behavior or am I doing something wrong?

Can confirm that I am having the same issue. Have you figured out a fix?

If you have a look at the time-based pagination section of the Graph API docs, you can see that the since parameter is defined as

A Unix timestamp or strtotime data value that points to the start of the range of time-based data.

I would always use unix timestamps. Also the underlying library uses since, which seems to work.
The actual call is made via https://github.com/tobilg/facebook-events-by-location-core/blob/master/lib/eventSearch.js#L189 which seems reasonable as well.

any updates @valmcc @pmadruga?

Hi, yes it appears that my problems arose from events that were returned, that weren't within the dates that I specified. e.g. if I was to find events between 14th of March and 15th of March it would also give events on the 16th of March. I suspect it does this when it runs out of events between the 14th and 15th to give. I just filtered the output and it seems to be fine now.

You either need to specify the since and until values either specified as Unix timestamp, or as strtotime value.

it is the version 10 of the api and i still have the same problem even in the graph api

The whole api is deprecated since years @SAVE-POlNT

well, i'm still able to get the leads from ads from it , but in order to get new ads i have to navigate through all the old ones , sometimes i run the script for like 1 min to get only 2 new leads , maybe we are missing something , they are using graph api right ? we can query the data with it no ?


setTimeout duration in listen.js

Hello! I tried to increase the setTimeout duration in currentlyRunning = setTimeout(listen, Math.random() * 200 + 50) to reduce the frequency of polling for messages to the equivalent of five minutes or so, but it doesn't seem to work as expected (basically no messages were received as far as I can tell). Does anyone know why this is the case? Thank you!

It doesn't work this way... Facebook uses long pooling, so this api sends new request just after getting the response for the last one.

Now it makes sense, thanks for your reply!


Themes: get helper, querying by slug not working

Issue Summary
The get helper doesn't seem to work with the find-by-slug example from the docs.
{{#get "posts" slug="welcome-to-ghost"}} {{#post}}
{{title}}

 {{content}}
 {{/post}} {{/get}}
Steps to Reproduce

Enable the public API
Open index.hbs and paste the find-by-slug example from the docs
Edit the slug to match a published post
Restart the Ghost service
Reload browser page

Nothing is output. I tried the tag cloud example from the docs which worked fine.
Technical details:

Ghost Version: 0.11.7, self-hosted
Node Version: 4.7.3
Browser/OS: Firefox 52 on Android
Database: SQLite

Hey @thorsten-panknin 👋
This doesn't work for me neither. Sorry for trouble.
A workaround for you would be to use the following syntax:
{{#get "posts" slug="welcome-to-ghost"}}
  {{#foreach posts}}

{{title}}

  {{/foreach}}
{{/get}}

There is no problem with the result of the api response, the post is there, just the #post notation does not work. The #get result does not contain a post attribute. I will keep the issue open, will figure out why.

As I put in Slack, I did a quick investigation and am pretty baffled. This has NEVER worked.
It seems I confused myself. Section 4.1 of this issue: https://github.com/TryGhost/Ghost/issues/5993 explains the problem correctly. The documentation is totally not correct :disappointed:
If you use a blockParam like as |post| it would work:
{{#get "posts" slug="welcome-to-ghost" as |post|}}
{{#post}}

{{title}}

 {{content}}

{{/post}}
{{/get}}

Although it does switch between doing either a read or browse request as the docs suggest, the response format is identical. Both return an array, even though the read request only returns a single item.
There is no flattening or extra handling, so unless you use a block param as described above, you would need to use {{#foreach}} unlike what the docs say.
I am absolutely not sure how I managed to confuse myself here, but this is effectively an error in the documentation - all responses from the get helper are entirely consistent so the documentation is just confusing things!
Gonna count this as a docs bug & fix the docs to say that all results are the same.

@kirrg001 Thanks, the workaround works fine.
@ErisDS Thanks for your efforts as well.

Same problem with querying by id in the documentation. Should be updated.

I have updated http://themes.ghost.org/docs/get and http://themes.ghost.org/v0.11.9/docs/get 👍
Thanks again for the report 😎


Viewing posts results in page getting stuck on loading screen

Site
phanpy.social
Version
2<IP_ADDRESS>bd3b3
Instance
meow.social
Browser
Firefox 131.0 on Linux
Firefox 131.0.2 on Linux
Firefox 131.0.3 on Linux
Bug description
Any attempt to view a post (i.e. by clicking a post on the home feed, clicking "View post" button in media view, clicking post in notifications menu, etc.) causes the page to get stuck on a loading screen. Attempting to click out of the unloaded post changes the URL in the address bar of the browser, but does not successfully exit the loading screen. The only way out of this state is to reload or close the tab.
The loading view where the page becomes stuck:

Clicking outside of the unloaded post changes URL in address bar, but does not update page until tab is refreshed:

Refreshing while still inside post causes home feed in background to appear to load indefinitely as well:

To reproduce

Install any of the listed Firefox versions on Linux (I am unsure of exactly when this issue was introduced, but it occurs reliably on all three of those versions for me)
Go to your home feed on phanpy.social
Click any post; it will fail to display the enlarged post and appear to load indefinitely

Expected behavior
The post should open in the enlarged view, as it does on other browsers/platforms, and clicking outside of the post should successfully exit to the previous view.
Other
No response

@o-dawgie this is a little difficult for me to find the cause. Are you able to open devtools and see if there are any related errors in the console? 🙇♂

@o-dawgie is it possible for you to test if this bug happens on the dev site too? (https://dev.phanpy.social/)
If the bug happens there, I can immediately apply a fix and ping you to check again, as deployment is faster on dev site than production 🙇♂

@o-dawgie try again.


CRD fqdn regex is too strict

Fixes #821
Allow numbers in TLD.
Example:   my.domain.k8s

@davecheney If I make the same changes and sign the commit, will that be merged?  I want his PR to get merged but the gentle nudges don't seem to be working.

@troy0820 sorry, that is not possible.

No problem, I closed the PR.

Thank you. I'm sorry it has to be this way, the lawyers need to see a clean
chain of custardy from any change to the person who wrote it. I know your
intentions were to be helpful but sadly the DCO process does not have a
provision for good intentions.
On Wed, 19 Dec 2018 at 09:08, Troy Connor<EMAIL_ADDRESS>wrote:

No problem, I closed the PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/heptio/contour/pull/822#issuecomment-448389216, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAcA6S9ddlqMy9zzmN3QbSGRoJyecUmks5u6WdigaJpZM4Y2Zz0
.


mount-buildkite-agent being true by default is a footgun

We're using the docker-buildkite-plugin to achieve a basic level of build isolation to make it safer to run pull requests from third-party forked repositories.
However, for this to be effective, we need to make sure we set mount-buildkite-agent: false for each invocation of the docker-buildkite-plugin, as otherwise the agent token is leaked into the docker container, allowing a malicious PR author to run arbitrary pipelines on our build agents.
I'd like to suggest that mount-buildkite-agent should be false by default.

This is a great suggestion. I have created #211 implementing the change which will result in an update to the major version of the plugin as it would be a backwards-incompatible change


Free Druid source code from Guava by shading

Fixes #6942
Description
This might look like a large PR but most changes are mechanical i.e. updates to import statements and guava dependency in various pom files.
Here is the meaty part...

A new module "shaded-guava" is introduced that produces classes in "org.apache.druid.com.google.common" package by shading real guava. See shaded-guava/pom.xml .
pom.xml in all modules are made to depend upon shaded guava jar above instead of real guava, that change looks like

-      <groupId>com.google.guava</groupId>
+      <groupId>org.apache.druid.com.google.guava</groupId>

In all Java files, import com.google.common.X is replaced by import org.apache.druid.com.google.guava.X
"Organize Imports" is done to all Java files to correct import ordering or checkstyles fails
Some imports in cloudfiles-extensions and sql modules are reverted to use import com.google.common.X because their dependencies jclouds-core and calcite respectively mandate using real import com.google.common.X in various methods exposed by those libraries. But this is minimal.
some imports that used org.apache.curator.shaded.com.google.common.X , i.e. shaded version of guava used by curator, continue to use same. that is independent.

(this approach was briefly described in https://github.com/apache/druid/issues/6942#issuecomment-791029487 )
End Result is that Druid source code is free from real guava and can use any version of guava inside shaded-guava module, few exceptions in (5) as described above.
we still ship guava-0.16.1.jar like before, so no external integrations should see any impact. User should be able to switch this with their favorite version of guava jar at runtime and Druid source code be fine because it uses druid-shaded-guava-0.x.y.jar
Existing Unit, Integration Tests and Travis builds should cover all of the changes except for Hadoop Integration that I could not verify due to not having quick access to such setup. However, given the way this patch works and that we continue to ship existing guava jar, Hadoop Integration should see no change.
https://github.com/apache/druid/issues/10965 should also be done after this PR is accepted.

This PR has:

[x] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[ ] added documentation for new or modified features or behaviors.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[ ] been tested in a test Druid cluster.

Ah, this PR is very prone to merge conflicts due to the sweeping changes made. However, this PR can be reviewed in the presence of conflicts [with mechanical changes described in PR description]. I will fix all the conflicts when this PR is accepted and ready to be merged.

This looks good to me. @himanshug when are we planning to commit this?

@mghosh4 needs to get review/approval before it can be merged.

Looks good, @himadrisingh  I wonder if extensions-core/hive-extensions/pom.xml was added by mistake?

Looks like ambari-metrics-emitter will fail without guava 16:
mvn dependency:tree
...
[INFO] +- org.apache.ambari:ambari-metrics-common:jar:<IP_ADDRESS>.0:compile
[INFO] |  +- commons-logging:commons-logging:jar:1.1.1:compile
[INFO] |  +- com.google.code.gson:gson:jar:2.2.2:compile
[INFO] |  +- com.google.guava:guava:jar:16.0.1:compile

Looks good, .. I wonder if extensions-core/hive-extensions/pom.xml was added by mistake?

yes

We need to merge the ticket, it will solve a bunch of problems and people waiting for it.

@egor-ryashin Thanks. Unfortunately I will not be able to spend much time on it in the near future. Please feel free to take the commits here , create a new PR with conflicts resolved and any other files that were added later.


Nvidia gpu docker image

Need help compiling a docker image for nvidia gpus. The project needs to be compiled on an nvidia cuda image.
I don't have the required resources to compile an image and my builds keep failing. Any help with this would be appreciated.
We simply need to use a nvidia-cuda docker image as base,
enable the nvidia flag while running make on whisper
Rest of the steps remain the same.

@rishikanthc I have been digging now: My previous error was a fault with pocketbase. Here is my actual error log. Let me know if I can test something.
==========
== CUDA ==
==========

CUDA Version 12.2.0

Container image Copyright (c) 2016-2023, NVIDIA CORPORATION & AFFILIATES. All rights reserved.

This container image and its contents are governed by the NVIDIA Deep Learning Container License.
By pulling and using the container, you accept the terms and conditions of this license:
https://developer.nvidia.com/ngc/nvidia-deep-learning-container-license

12:26:57 PM [vite-plugin-svelte] /app/src/lib/components/FilePanel.svelte:366:7 A11y: Avoid using autofocus
364:               class="h-[30px] w-[300px] rounded-md border border-carbongray-300 p-1 focus:outline-none focus:ring-2 focus:ring-carbongray-800 focus:ring-offset-2 focus:ring-offset-white disabled:bg-carbongray-50 dark:bg-carbongray-700 disabled:dark:bg-carbongray-600"
A copy of this license is made available in this container at /NGC-DL-CONTAINER-LICENSE for your convenience.
365:               on:keydown={handleKeydownRecord}
366:               autofocus
                   ^
367:               disabled={renameLoading}

368:             />
12:26:57 PM [vite-plugin-svelte] /app/src/lib/components/FilePanel.svelte:374:5 A11y:
 with dblclick handler must have an ARIA role
372:

373:         {:else}
WARNING: The NVIDIA Driver was not detected.  GPU functionality will not be available.374:

               ^
375:             {selected?.title}
376:

12:26:57 PM [vite-plugin-svelte] /app/src/lib/components/FilePanel.svelte:396:7 A11y: Avoid using autofocus
394:               class="h-[30px] w-[300px] rounded-md border border-carbongray-300 p-1 focus:outline-none focus:ring-2 focus:ring-carbongray-800 focus:ring-offset-2 focus:ring-offset-white disabled:bg-carbongray-50 dark:bg-carbongray-700 disabled:dark:bg-carbongray-600"
395:               on:keydown={handleKeydown}
396:               autofocus
   Use the NVIDIA Container Toolkit to start this container with GPU support; see
   https://docs.nvidia.com/datacenter/cloud-native/ .
                   ^
397:               disabled={renameLoading}

Creating admin with email: myemail@myemail
PocketBase URL: http://mylocalip:8080

><EMAIL_ADDRESS>build
398:             />
> vite build
12:26:57 PM [vite-plugin-svelte] /app/src/lib/components/FilePanel.svelte:404:5 A11y:
 with dblclick handler must have an ARIA role
402:

403:         {:else}
404:

               ^

405:             {selectedTemplate?.title}
406:

12:26:58 PM [vite-plugin-svelte] /app/src/lib/components/UploadPane.svelte:84:1 A11y: visible, non-interactive elements with an on:click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as <button type="button"> or  might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.
82:

83:
84:   <div
      ^
vite v5.4.7 building SSR bundle for production...85:     class="my-4 flex h-[150px] w-full cursor-pointer items-center justify-center border border-dashed border-carbongray-200 text-carbongray-300 dark:border-carbongray-600"

86:     on:dragover={handleDragOver}
12:26:58 PM [vite-plugin-svelte] /app/src/lib/components/UploadPane.svelte:84:1 A11y:
 with dragover, drop, click handlers must have an ARIA role
82:

83:
84:   <div
      ^
85:     class="my-4 flex h-[150px] w-full cursor-pointer items-center justify-center border border-dashed border-carbongray-200 text-carbongray-300 dark:border-carbongray-600"
86:     on:dragover={handleDragOver}
12:26:58 PM [vite-plugin-svelte] /app/src/lib/components/Processing.svelte:14:1 Unused CSS selector ".dot-container"
12:
transforming...13:


Regression in BackdropFilter performance on Android

SkiaPerf is reporting regressions in raster time for the BackdropFilter family of benchmarks on the Engine roll here https://github.com/flutter/flutter/pull/109466 that contains only https://github.com/flutter/engine/pull/35022, the change to enable DRM support in the Embedder API.
https://flutter-flutter-perf.skia.org/e/?begin=1659653286&end=1660881566&keys=X9dc74513e30b4a61d2a14daea5bab12d&requestType=0&xbaroffset=30464
cc @iskakaushik @betrevisan

Possibly unrelated is a regression in picture cache count https://flutter-flutter-perf.skia.org/e/?begin=1660297344&end=1660361973&keys=X1f8af34026d827e5c17dd7996ddd8f90&num_commits=50&request_type=1&xbaroffset=30464

Thanks!


Adding Disqus - Error: While parsing config: (7, 21): never reached

while following the quickstart, at Step "10. Integrate Disqus"
http://gohugo.io/overview/quickstart/
I copy/pasted as specified, to give me this:
baseurl = "http://blog.example.com/"
title = "example"
languageCode = "en-gb"

[Params]
  Author = "Peter"
  disqusShortname = blog-example-com

And tried to build:
C:\Users\peter\git\blog>hugo
Error: While parsing config: (7, 21): never reached

Removing the [params] stanza restores things to normal

Try to wrap blog-example-com in quotes, like it was done with Author's value. Please refer to the Hugo forum for such questions.

Oh good call, thanks. Quoting it seems to have fixed the error.
Just reading through the .toml spec and apparently dashes are perfectly valid when not quoted.
https://github.com/toml-lang/toml#keyvalue-pair
Is this a toml bug I should raise or a Hugo bug do you think?

Is this a toml bug I should raise or a Hugo bug do you think?

String values must be quoted. This is how I read the spec.

The toml spec? where do you read that?

Keys may be either bare or quoted. Bare keys may only contain letters, numbers, underscores, and dashes (A-Za-z0-9_-). ... Best practice is to use bare keys except when absolutely necessary.

*value not key

Important distinction which I glossed over! Got it, thanks.


[question] About how assets are generated

I am sorry to ask you this way,
can you tell me how the assets/assets.go file was generated, thanks

At the same time, I found that executing the top command after running gotty zsh will crash the page.

Maybe commit 6a97c5657edb707e04828e8b1f3a3be4fe220a9a is correct,
Also, can we try to upgrade xterm.js to the latest version? Looking forward to your reply.


BoneCP also tested???

I wonder who is responsible for the output of:
04:49:427 [Timer-3] INFO DbDownTest - BoneCPDataSource got a connection.
?
I thought you only tested C3P0, Tomcat DBCP2, Vibur and Hikari.

Bone was removed because the author stop development of the pool, and I wanted to focus on active projects.

I see. Thank you. So maybe it would be a good hint to remove the line in the log or to annotate it in the article what you told me.


Update ClimaCore, switch to using tuples instead of Refs

Purpose
Test out latest ClimaCore, including memory fixes (https://github.com/CliMA/ClimaCore.jl/pull/1113)
To-do

Content

[ ] I have read and checked the items on the review checklist.

This is blocked by https://github.com/CliMA/ClimaCore.jl/pull/1124

Need to track down the source of allocations: https://buildkite.com/clima/climaatmos-ci/builds/7041#01863c95-215c-4179-826e-6fa4667e8dd8

Looks like EDMF is causing problems, will need to look into it

Okay, I think this is ready once we tag a new ClimaCore.

I haven’t looked at the ci. @simonbyrne do you expect behavior change?

The results look fine to me. @simonbyrne if you expect behavior change for this PR, and think the allocation change is ok, I can fix the mse and merge it.

no, i don't expect any behavior change

no, i don't expect any behavior change

Oh, but the mse table suggests that there are behavior changes?

yeah, i'm not sure what is going on there. Has something changed, because the last test I ran passed: https://buildkite.com/clima/climaatmos-ci/builds/7670#01869ef2-cb56-4b5e-ac81-6f22081d07ae

The only PRs that changes mse between Wednesday and now are #1398 and #1327 I think

yeah, i'm not sure what is going on there. Has something changed, because the last test I ran passed: https://buildkite.com/clima/climaatmos-ci/builds/7670#01869ef2-cb56-4b5e-ac81-6f22081d07ae

The ref_counter was bumped from 73->74 in the last build (linked above) - this means the system treats it as a self-reference and that would pass the CI build right ?

okay, i started a longruns build: https://buildkite.com/clima/climaatmos-longruns/builds/838

The results look fine to me.
longrun_hs_rhoe_highres_hightop

longrun_hs_rhoe_equilmoist_highres_hightop_rayleigh30e3

bors r+

bors r+


Create index.html for Homepage

This task involves creating the index.html file for the Homepage project.

I have created the initial version of the index.html template.


Scrollbar fixes

Pull request type
Updated the (Dynamic)ScrollBar default style to be more inline with WinUI addressing: #872

Added on hover background color (couldn't use InAppAcrylicDefaultBrush like in WinUI, but used the replacement color we also use for e.g. Flyout)
Decreased scrollbar thumb width based on WinUI spec
Decreased icon fontsize so it's centered and inline with WinUI spec

Before:

After:

ScrollBar now overlaps content, addressing: #871

Tweaked the default ScrollViewer style so it overlaps its content
Set a default style for PassiveScrollViewer so it uses the ScrollViewer style as well (as ListView uses PassiveScrollViewer)
Before:

After:

Please check the type of change your PR introduces:

[ ] Update
[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Other information

@pomianowski In case this PR gets approved, would you mind creating a Preview.13 :)?


CORE-230 - Refactor Admin Permissions

This PR refactors our bespoke Roles and Permissions into the package provided by Spatie.
This will be useful ahead of the Nova implementation.
Some things to note...

Tests across Adm are poor but will no longer be required once we push Nova.
The migrations will delete all existing role allocations to users and permission allocations to roles. The hope here is that this will allow us to start fresh and allocate only the permissions that users require.
The implementation of this is not designed to be perfect, nor is it designed to be long term. It is supposed to get us by until we have the ability to deploy Nova and take advantage of proper policies.

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


MyClass number get, set and print function results are all zero

class MyClass

@ouyangyiluo Please expand on the issue being reported here. They are all zero because that is the initial value. Calling the properties in C++ can change that. Let me know what you've tried so far.

@ouyangyiluo请扩展此处报告的问题。它们都为零，因为那是初始值。在 C++ 中调用属性可以改变这一点。让我知道你到目前为止所做的尝试。

I am using
Visual Studio 2022 Preview
.NET 5.0。
My test result .

After trying to modify the code, the test result is the same as that of C#
`    public class MyClass
{
public MyClass()
{
Number = 0;
}
    public int Number { get; set; }

    public void PrintNumber() => Console.WriteLine(Number);
}`


Fix sorting by column in the GUI

Previously clicks on the header sections were ignored.

LGTM, thanks!


Update publications component to match refined mocks. #86.

Reviewers
#86
@MillenniumFalconMechanic
Changes

added publications component.
added publications story and publications story to project story.
added publications to projectTransformer and projectViewModelBuilder.
updated project entities with project related interfaces.

Thank you so much @MillenniumFalconMechanic ❤


Load wordlist relative to calling directory instead of module directory

Issue fixed that I referenced in #3

I know this is a very minor change to a very small library, but I'm just doing spring cleaning and saw my dangling PR. If you read the issue I posted, you can see the problem it fixes and how it improves the functionality / brings it more in-line with what may be expected based on existing node modules.

Sweet! I know it's dumb, for some reason that was really buggin me.

😄 Sorry that it took this long to merge, I have been busy taking care of family.
Thanks for the PR!
-R


[help wanted] How to auto jump new route.

componentDidMount() {
  // jump new route
}

In ./Example :
When Actions.register() in ./Example.js, it can work. But it can not work when Actions.register() in ./components/Launch.js.

Please use search before posting. Duplicate of #253.


Code sample update request

At link:
http://docs.identityserver.io/en/release/quickstarts/1_client_credentials.html
... the code needs this line to work: using IdentityServer4.Models;
Otherwise, adding ApiResource and Client reference is not recognized.

PR on the docs is welcome.

docs are being re-worked right now. And yes - PRs are welcome.


Type: Bug
Enter Task Name: PackerBuildV1
Environment
Server is Azure Pipelines.
Agent is Hosted.
Issue Description
Images created with the Packer build step still have the packer user present in a sudoers file.
Here is the relevant file after provisioning a VM from an image created with the PackerBuild task.
$ sudo cat /etc/sudoers.d/90-cloud-init-users
# Created by cloud-init v. 21.1-19-gbad84ad4-0ubuntu1~20.04.2 on Mon, 14 Jun 2021 15:03:37 +0000

# User rules for packer
packer ALL=(ALL) NOPASSWD:ALL

# User rules for testadminuser
testadminuser ALL=(ALL) NOPASSWD:ALL

testadminuser is the admin username I provisioned the VM with. It is expected that this user is present in this file.
I believe the line packer ALL=(ALL) NOPASSWD:ALL should have been removed as part of cleanup during the PackerBuild task.

This issue is still present.


Compact sidebar

General information
This PR has improvements to the readability of the gene info in the sidebar.
Associated issues:

#16

Checklist
Author:

[x] One or more reviewers have been assigned.
[x] N/A: Automated tests have been included in this pull request, if possible, for the new feature(s) or bug fix.
[x] The associated GitHub issues are included (above).
[x] Notes have been included (below).

Reviewers:

[ ] All automated checks are passing (green check next to latest commit).
[ ] At least one reviewer has signed off on the pull request.  Reviewers have two business days to review the pull request, after which the author may merge in the pull request unilaterally.

Notes

Round the rank to 2 digits after the decimal point.  Use GENE_RANK_ROUND_DIGITS to configure.
Include the rank number on the bar.  This makes it clear that the number represents the same value as the bar.  It also saves a lot of space so you can see more genes without scrolling.
The caret to expand and collapse a gene is softened.  This makes the gene name stand out more, making it easier to read the list.
This uses inlines styles, since it looks like the sidebar is going that way.

Before:

After:

I like how it looks in the screenshot you attached, but the problem is that the bar is not always aligned to the left (see my screenshot below).
Also, if the bar is too small, the text has poor contrast against the black chart background.

Do you have an example file for that?  The small network doesn't have any negative values.  I tried the large example and it crashes the browser.  The services are also slow for the large example (2+ minutes).

You can use this sample file I made much smaller just for these kind of tests. Thanks!
Supplementary_Table2_MesenvsImmuno_RNASeq_ranks_XSMALL.txt

Could you test this out for edge cases you can think of?  I'm not sure of all the details of how your bars work, but I think my math should check out for positioning.

What do you think of these colours?

I chose orange/purple from Color Brewer because they are 'hot' (positive) and 'cold' (negative) with no the usual associated meanings, such as 'good' (e.g. green) or 'bad/forbidden' (e.g. red).
But I agree your colours look better to the eye. So as long as they are color-blind safe, go ahead! They look great!


Fix AddClearanceToUsers down method (remove_index)

Currently, the self.down method of the AddClearanceToUsers migration only removes the columns, but not the indexes.
So if you migrate and then rollback, you can no longer migrate:
rails db:migrate
==<PHONE_NUMBER>5500 AddClearanceToUsers: migrating ==============================
-- change_table(:users)
   -> 0.0212s
-- add_index(:users, :email)
rails aborted!
StandardError: An error has occurred, this and all later migrations canceled:

PG::DuplicateTable: ERROR:  relation "index_users_on_email" already exists
/home/hans/projects/dummy/db/migrate/20210212135500_add_clearance_to_users.rb:9:in `up'
/home/hans/projects/dummy/bin/rails:9:in `<top (required)>'
/home/hans/projects/dummy/bin/spring:15:in `<top (required)>'

Caused by:
ActiveRecord::StatementInvalid: PG::DuplicateTable: ERROR:  relation "index_users_on_email" already exists
/home/hans/projects/dummy/db/migrate/20210212135500_add_clearance_to_users.rb:9:in `up'
/home/hans/projects/dummy/bin/rails:9:in `<top (required)>'
/home/hans/projects/dummy/bin/spring:15:in `<top (required)>'

Caused by:
PG::DuplicateTable: ERROR:  relation "index_users_on_email" already exists
/home/hans/projects/dummy/db/migrate/20210212135500_add_clearance_to_users.rb:9:in `up'
/home/hans/projects/dummy/bin/rails:9:in `<top (required)>'
/home/hans/projects/dummy/bin/spring:15:in `<top (required)>'
Tasks: TOP => db:migrate
(See full trace by running task with --trace)

This fix adds the remove_index calls to the self.down method.

Thank you for opening this PR @Spone!
I tried to reproduce this and failed. I set up a test rails app with sqlite and:

Installed clearance
Ran the generator script
Rolledback
Migrated again

This completed successfully:
~/Code/thoughtbot/clearance_test main*
❯ bin/rails db:migrate
==<PHONE_NUMBER>2157 CreateUsers: migrating ======================================
-- create_table(:users)
   -> 0.0016s
-- add_index(:users, :email)
   -> 0.0010s
-- add_index(:users, :remember_token)
   -> 0.0006s
==<PHONE_NUMBER>2157 CreateUsers: migrated (0.0032s) =============================

~/Code/thoughtbot/clearance_test main*
❯ bin/rails db:rollback
==<PHONE_NUMBER>2157 CreateUsers: reverting ======================================
-- remove_index(:users, :remember_token)
   -> 0.0020s
-- remove_index(:users, :email)
   -> 0.0009s
-- drop_table(:users)
   -> 0.0007s
==<PHONE_NUMBER>2157 CreateUsers: reverted (0.0061s) =============================

~/Code/thoughtbot/clearance_test main*
❯ bin/rails db:migrate
==<PHONE_NUMBER>2157 CreateUsers: migrating ======================================
-- create_table(:users)
   -> 0.0016s
-- add_index(:users, :email)
   -> 0.0008s
-- add_index(:users, :remember_token)
   -> 0.0007s
==<PHONE_NUMBER>2157 CreateUsers: migrated (0.0032s) =============================

Could you share more details about your configuration to help me reproduce this issue?
Thanks!

@Spone Which database and Rails version are you using? I think that before rails 4 removing the column would not necessarily remove the index

Hi, sorry for the delay. I'm using Postgres with Rails <IP_ADDRESS>.
My users table primary key is a uuid, and I think it may be the cause of the issue.
I managed to reproduce the issue on a fresh Rails install.
Create this migration:
class CreateUsers < ActiveRecord::Migration[6.1]
  def change
    enable_extension 'pgcrypto' unless extension_enabled?('pgcrypto')

    create_table :users, id: :uuid, default: 'gen_random_uuid()' do |t|
      t.string :name
      t.string :email

      t.timestamps
    end
  end
end

Then run:
$ rails generate clearance:install
$ rails db:migrate
==<PHONE_NUMBER>1117 CreateUsers: migrating ======================================
-- extension_enabled?("pgcrypto")
   -> 0.0025s
-- create_table(:users, {:id=>:uuid, :default=>"gen_random_uuid()"})
   -> 0.0166s
==<PHONE_NUMBER>1117 CreateUsers: migrated (0.0194s) =============================

==<PHONE_NUMBER>1137 AddClearanceToUsers: migrating ==============================
-- change_table(:users)
   -> 0.0066s
-- add_index(:users, :email)
   -> 0.0034s
-- add_index(:users, :remember_token)
   -> 0.0100s
-- select_all("SELECT id FROM users WHERE remember_token IS NULL")
   -> 0.0037s
==<PHONE_NUMBER>1137 AddClearanceToUsers: migrated (0.0241s) =====================

$ rails db:rollback
==<PHONE_NUMBER>1137 AddClearanceToUsers: reverting ==============================
-- change_table(:users)
   -> 0.0033s
==<PHONE_NUMBER>1137 AddClearanceToUsers: reverted (0.0034s) =====================

$ rails db:migrate
==<PHONE_NUMBER>1137 AddClearanceToUsers: migrating ==============================
-- change_table(:users)
   -> 0.0053s
-- add_index(:users, :email)
rails aborted!
StandardError: An error has occurred, this and all later migrations canceled:

PG::DuplicateTable: ERROR:  relation "index_users_on_email" already exists
/home/hans/projects/sandbox/debug_clearance/db/migrate/20210412221137_add_clearance_to_users.rb:9:in `up'
/home/hans/projects/sandbox/debug_clearance/bin/rails:5:in `<top (required)>'
/home/hans/projects/sandbox/debug_clearance/bin/spring:10:in `block in <top (required)>'
/home/hans/projects/sandbox/debug_clearance/bin/spring:7:in `tap'
/home/hans/projects/sandbox/debug_clearance/bin/spring:7:in `<top (required)>'

Caused by:
ActiveRecord::StatementInvalid: PG::DuplicateTable: ERROR:  relation "index_users_on_email" already exists
/home/hans/projects/sandbox/debug_clearance/db/migrate/20210412221137_add_clearance_to_users.rb:9:in `up'
/home/hans/projects/sandbox/debug_clearance/bin/rails:5:in `<top (required)>'
/home/hans/projects/sandbox/debug_clearance/bin/spring:10:in `block in <top (required)>'
/home/hans/projects/sandbox/debug_clearance/bin/spring:7:in `tap'
/home/hans/projects/sandbox/debug_clearance/bin/spring:7:in `<top (required)>'

Caused by:
PG::DuplicateTable: ERROR:  relation "index_users_on_email" already exists
/home/hans/projects/sandbox/debug_clearance/db/migrate/20210412221137_add_clearance_to_users.rb:9:in `up'
/home/hans/projects/sandbox/debug_clearance/bin/rails:5:in `<top (required)>'
/home/hans/projects/sandbox/debug_clearance/bin/spring:10:in `block in <top (required)>'
/home/hans/projects/sandbox/debug_clearance/bin/spring:7:in `tap'
/home/hans/projects/sandbox/debug_clearance/bin/spring:7:in `<top (required)>'
Tasks: TOP => db:migrate
(See full trace by running task with --trace)

After investigating this it seems that the cause of the issue is that your CreateUsers migration does not add an index to the email column, so the migration that clearance creates adds it on up but it's then not removed on down. The other index we add is remember_token, but that one doesn't cause an issue because we are also adding/removing the column.
I think your proposed changes would fix this, but I want to take some time to make sure there won't be any side effects to this before merging it.


[T2A1][T01-T4]Lui Sheng Jie

Ready for review

@luishengjie Some comments added. Please close the PR after reading comments.

@luishengjie Some comments added. Please close the PR after reading comments.


GraphQL - Support for JS pipeline resolves

Is this feature request related to a new or existing Amplify category?
api
Is this related to another service?
AppSync
Describe the feature you'd like to request
At present, Amplify only supports extending the Amplify-generated resolvers for GraphQL APIs using VTL.
AppSync now supports writing pipeline resolvers in JS.
Describe the solution you'd like
Support for extending Amplify-generated resolvers using JS.
Describe alternatives you've considered
Writing custom pipeline resolvers in VTL is of course possible, but generally makes for a less pleasant developer experience (harder to test, less familiar syntax).
Business logic can also be encapsulated within a Lambda function resolver. However, when the required logic is relatively simple (e.g. performing some extra validation before a Create/Update operation), this feels like overkill.
Additional context
No response
Is this something that you'd be interested in working on?

[ ] 👋 I may be able to implement this feature request

Would this feature include a breaking change?

[ ] ⚠ This feature might incur a breaking change

It seems that this is duplicate of aws-amplify/amplify-category-api#1015


fix: upgrade @xstate/react

:tada: This PR is included in version 1.2.5 :tada:
The release is available on:

1.2.5
GitHub release
1.2.5

Your semantic-release bot :package::rocket:


Usage with gatsby-plugin-intl is not working

I want to use this package together with gatsby-plugin-intl
By using gatsby-plugin-intl I always need to make my imports from this plugin.
import { injectIntl } from "gatsby-plugin-intl";

instead of
import { injectIntl } from "react-intl";

Unfortunately this breaks the auto generation of the IDs and I'm getting the error:
[React Intl] An `id` must be provided to format a message.

I fixed this by importing something from the "react-intl" package even if I don't use it in my component.
import { useIntl } from "react-intl";

This way it works but I wonder if there is a better solution how I can fix this?

@saschametz Please upgrade to v2.3.0. Then add the following to .babelrc
{
  "plugins": [
    [
      "react-intl-auto",
      {
        "moduleSourceName": "gatsby-plugin-intl"
      }
    ]
  ]
}

@akameco It's working now. Thank you very much


TypeError: init() got multiple values for argument 'use_technical_indicator'

How can I solve this problem. I looked at the API, but it didn't work
Perform Feature Engineering:
df = FeatureEngineer(df.copy(),
use_technical_indicator=True,
tech_indicator_list = config.TECHNICAL_INDICATORS_LIST,
use_turbulence=True,
user_defined_feature = False).preprocess_data()

Hello! I believe that the implementation of the FeatureEngineer may have changed under you. Please pull the latest code and try again. If you encounter issues, please open another ticket.

Hello! I believe that the implementation of the FeatureEngineer may have changed under you. Please pull the latest code and try again. If you encounter issues, please open another ticket.

Hi. I have the exact same error. I installed the latest version of Feature Engineer, but I get the error nonetheless.

I also tried this installation.


Add modeling rule for joining too many models

Describe the feature
Per the best practices docs:

Structural simplification. Bringing together a reasonable number (typically 4 to 6) of entities or concepts (staging models, or perhaps other intermediate models) that will be joined with another similarly purposed intermediate model to generate a mart — rather than have 10 joins in our mart, we can join two intermediate models that each house a piece of the complexity, giving us increased readability, flexibility, testing surface area, and insight into our components.

Would you be keen to take this one on?

Thanks for the response @b-per. Sorry, I don't have time right now.

Hey brad! yep that's about it! it would look like:

adding a fct_ model to the modeling marts directory, with logic like you described! I might suggest lowering the barrier to 7 or more parent models :)
Adding the is_empty test to that model (as other models have) to raise the expected warning
adding a model in the integration_tests folder that violates this rule, to ensure it's working as intended.
Add a seed to the integration_tests/seeds directory that matches the expected output of the fct_ model you added

Let me know if that makes sense! happy to help shepherd that along

Thanks, Dave.
Where you mention adding the new fct_ model to the modeling marts directory, I don't see a "modeling" directory under models/marts/. Is the /models/marts/dag directory a good place for the new fct_ model?
I will also need to add information about this model to the docs/rules/modeling.md file, right?

I've completed making the changes as you've mentioned. In addition, I updated the docs to explain the new model. For the screenshots I had two concerns; When I attached the screenshots they are linked to my repository (not sure if that gets automatically updated or if it's something that a dbt maintainer would have to deal with) and the screenshots are from the new Cloud Lineage diagram, so the look and feel is different from the existing screenshots.
The thing I haven't been able to figure out is how to run the integration_tests. I am working on VSCode and cloned my repository, I am able to build and run the new model (on Duckdb) but I can't figure out how to have it run the models in the integration_tests. Are there instructions on how to do that? The readme for this package is kind of light on details of how to actually do that test.
Otherwise, I think it's ready for review. Let me know if I should create the PR now, or if I need to figure out how to run the integration_tests and do that first.
Thanks!

@dave-connors-3 Sorry for the direct ping, I'm not sure if you get notified when a comment gets posted or only if you're tagged.
When you have time, can you look at my last 2 comments?
Thanks.

hey @BradCr! sorry for the delay!

Where you mention adding the new fct_ model to the modeling marts directory, I don't see a "modeling" directory under models/marts/. Is the /models/marts/dag directory a good place for the new fct_ model?

yes, dag! was going off of memory which is never a good idea
second off, would love if you opened a draft PR with your changes! Will definitely help to see your changes to speak a bit more intelligently!
thirdly, integration tests! if whatever i come up with here works for you, i'll add it to the docs for future contributors :)
The basic idea is that the integration_tests folder contains a dbt project with a bunch of dummy models that violate a whole bunch of the rules. This project imports the actual dbt_project_evaluator project as a local package, so when you run it, you'll build all the models in integration_tests as well as the ones from project evaluator. Then, there's a seed in the seeds folder for each of fct models that asserts what the output of the model should be from the integration_tests project. For example test_fct_missing_primary_key_tests asserts what the output of fct_missing_primary_key_tests should be given the models in the integration_tests project. This seed is configured with a dbt test to make that assertion! When all this is configured, a passing dbt build on this project means your integration tests are passing!
to run the integration tests:

if you haven't already, install dbt-duckdb (seems like you're good here)
add an integration_tests profile to your profiles.yml

integration_tests:
  outputs:
    duckdb:
      type: duckdb
      path: ./dbt.duckdb
  target: duckdb

add/edit the models in the project to introduce a violation that would be caught by your new rule
add a seed called test_{{ your new fct model name }} in the appropriate directory that contains the expected output of your new fct model
configure the equality test like in the above example
dbt build

A note that adding + editing models may cause failures in other integration tests in the case that you accidentally introduce violations of other rules. You can edit as necessary to get the output you expect.
that all make sense?

Thanks, @dave-connors-3, it's all making sense to me.
I'll give the integration tests another try and let you know how it goes. I think the only thing I hadn't yet done was the equality test between the seed (which I did create) and the model that violated the new rule (which I also did create). I didn't modify any of the existing seeds or violating-models.
I'll also open up the draft PR.
Thanks again for your help, I'm excited to keep moving.

So, here's a very bizarre thing I found out. In the root of the dbt-project-explorer I could run dbt deps just fine, but when I went into the integration_tests subfolder and ran dbt deps there, it would just hang at "Installing". That's why I wasn't able to do a dbt build inside that folder. I finally looked at the dbt.log and found this error message: "Symlinks are not available on this OS, copying dependency."
A Google search led me to this old Git issue: https://github.com/dbt-labs/dbt-core/issues/766, which talks about Admin user level access being required to run Symlinks on Windows. So when I ran VS Code as an Admin, the dbt deps ran just fine. Weird!
Anyhow, I'm now working on running the test and then I'll open the PR.

@dave-connors-3 I've created the draft Pull Request. https://github.com/dbt-labs/dbt-project-evaluator/pull/413