Remove @context so JSON only not JSON-LD

JSON with Immutable JSON Schema
The current VC examples include an @context. This will be removed. Either the @context is ignored which makes it pointless or if not ignored makes the VC insecure. In either case @context should not be used.
Problems with Linked Data based VCs
Linked data, i.e. JSON-LD based verifiable credentials require an @context. But this requirement makes them inherently insecure because the @context points to mutable schema. In general @context schema are derivatives or extensions to schema.org schema. Schema.org schema are mutable. The identifiers of schema.org schema do not have any inherent way to enforce immutability. Given such externally referenced mutable schema, a verifiable signature on a linked data verifiable credential does not ensure either the integrity nor the authenticity of the credential . This means that the over-the-wire VC may be subject to exploits that do not require compromise of the signing keys or the signature verification code. In other words, merely protecting private keys and signature verification code may be insufficient to guarantee security and secure verifiability. This may greatly expand the attack surface and therefore a serious design flaw for any linked data based verifiable credential system.
There are a couple of workarounds that one might suggest to address the mutability of the schema.org derived schema. One is to cache the schema and then use a hash link to reference the cashed schema. A hash link includes a cryptographic digest of the associated resource or data. But a hash link by itself is insufficient to ensure verifiability of the schema. The schema itself may mutate and the hash link merely makes that mutation detectable. The credential itself is still not verifiable unless the un-mutated schema is available someplace. This then imposes a forever constraint on the availability of the cached schema.  An attacker merely needs to attack schema.org to invalidate all linked data based VCs or attack any local caches.
We believe local caches to be an unreasonably cumbersome approach. And reliance on schema.org an unreasonably insecure approach. The root problem is using schema.org in the first place which was never designed to provide immutable schema for secure verifiable credentials but was designed for the now largely obsolete semantic web.
Another workaround is to not sign the over-the-wire schema but to sign the serialized fully expanded RDF graph that results from processing the VC with its schema. In this case a signature is signing an immutable representation of the VC. However these inverts the security layering such that one must process the payload (VC) before verifying the integrity and authenticity of that data. The RDF expansion stack now becomes part of the attack surface. Not to mention the performance hit associated with the expansion process. Moreover there are better more recent more widely adopted technologies for creating semantic graphs that makes RDF expansion a poor excuse for weakened security and performance degradation that results from signing the expanded not the over-the-wire VC. RDF was designed for the largely obsolete semantic web. Given that VCs are not meant for the semantic web, it seems a poor technology choice to burden VC with the largely obsolete technology that is linked data especially when there are more secure, widely adopted, powerful and performant alternatives.
GLEIF Approach
Consequently GLEIF is building its eco-system on secure immutable schema using the universally adopted JSON schema system but where those schema are secured by using content addressable cryptographic digest schema identifiers. Those schema may be provided in one of two secure ways. The first is to embed the schema in the verifiable credential itself thereby removing any availability issues. The second is to provide the schema via one or more highly available registries that ensure the immutable schema are indefinitely available. These verifiable data registries may be the same registries that host the issuance and revocation registries for the verifiable credentials themselves. The issuance and revocation registries must be both highly and indefinitely available. Thus no new meaningfully different burden is placed on the VC system to also support highly available immutable schema. The immutable schema registries also provide explicit extensible interoperability of schema type definitions as is the industry standard approach used by IANA class registries. The difference is that the schema type definitions for VCs must be immutable and any change to type definition requires a new identifier for that new type definition. Anything less exposes the VC system to security vulnerabilities.

Unlike schema.org and JSON-LD, JSON schema provides convenient support for custom schema and embedded custom schema via schema metadata files.
For example

Schema

{
  "id": "http://www.phvis.com/customerinforequest",
  "$schema": "http://json-schema.org/draft-04/schema",
  "title": "Customer Information Request",
  "version": "1.0.0",
  "type": "object"
  "properties": {
      "customerId": {
         "type": "string",
         "description": "This is the id that uniquely identifies the customer whose information is being requested."
         "pattern": "^[A-Z][0-9]{3}$",
         "default": "A000"
      }
  },

This issue was address in PR #4


Add developer docs on the EDMF numerics, filters and solved equations.

Translate Overleaf equations into ClimaAtmos documentation style:

discretised equations
clearly stated operators
boundary conditions
split between explicit/implicit tendencies
assumptions about equation constraints (positivity, etc)

Draft with the advection is here: https://github.com/CliMA/ClimaAtmos.jl/pull/1443


Upgrade fuel-core to 0.40.0

Release notes:

https://github.com/FuelLabs/fuel-core/releases/tag/v0.40.0

Looks like 0.40.0 introduced it's own max input validation making elements of #3328 - I'll get this over the line.

I found one issue but was confirmed as expected behaviour, have updated our testcase. I've left our validation in as I think it's quite intuitive for a scenario where a users gets a truncated getCoinsToSpend response and the tx fails as the AssetID is not present in the tx.

Impact of coins_to_spend now throwing for more than 255 coins from @xgreenx:

I don't think it can impact them, unless they have their ownserver-based application that fetch all possible coins and later cache them, but coins endpoint works better in this case

You can do nothing from your side if it breaks applications. The use case I described above shouldn't use coins_to_spend, we provide other endpoints that serves it better.

It is only can be handled on the application level by themself(if they used endpoint incorrectly).

Account.fund() which we use for the majority of our tx funding is using Provider.getResourcesToSpend which is using the coins_to_spend endpoint. Most people will be using our implementation rather than querying directly so I think this is a paticuarly vulnerable point for us. Going to migrate to get_coins today.

This better illustrates the problem for us:
import { ErrorCode, WalletUnlocked } from 'fuels';
import { expectToThrowFuelError, launchTestNode } from 'fuels/test-utils';

describe('Max Coins', () => {
  it('should be able to retrieve more than 255 coins', async () => {
    using launched = await launchTestNode();
    const {
      wallets: [wallet],
      provider,
    } = launched;

    const receiver = WalletUnlocked.generate({ provider });
    const assetId = provider.getBaseAssetId();

    // Generate 256 UTXOs for an account
    for (let i = 0; i < 256; i++) {
      const tx = await wallet.transfer(receiver.address, 1000, assetId);
      await tx.waitForResult();
    }

    // Get all the UTXOS using `get_coins`
    const getCoinsResInit = await receiver.getCoins(assetId, { first: 256 });
    expect(getCoinsResInit.coins.length).toBe(256);
    expect(getCoinsResInit.pageInfo.hasPreviousPage).toBe(false);
    expect(getCoinsResInit.pageInfo.hasNextPage).toBe(false);

    const getCoinsResNext = await receiver.getCoins(assetId, {
      first: 150,
    });
    expect(getCoinsResNext.coins.length).toBe(150);
    expect(getCoinsResNext.pageInfo.hasPreviousPage).toBe(false);
    expect(getCoinsResNext.pageInfo.hasNextPage).toBe(true);

    const getCoinsResLast = await receiver.getCoins(assetId, {
      after: getCoinsResNext.pageInfo.endCursor,
    });
    expect(getCoinsResLast.coins.length).toBe(106);
    expect(getCoinsResLast.pageInfo.hasPreviousPage).toBe(true);
    expect(getCoinsResLast.pageInfo.hasNextPage).toBe(false);

    // Get UTXOS using `get_coins_to_spend``
    await expectToThrowFuelError(() => receiver.getResourcesToSpend([[300_000, assetId]]), {
      code: ErrorCode.MAX_COINS_REACHED,
      message:
        'The account retrieving coins has reached the maximum response size. Please use the `getCoins` method to paginate the response.',
    });
  });
});

Given coins_to_spend now throws above 255 coins, we should add some docs detailing combining UTXOs..


Add algorithms in Go, Javascript, Perl, bash

I want to add some algorithms in Go. Please assign me.

Hey, I want to add algorithms in JavaScript. Please assign me.


psubscribe and punsubscribe in Cluster mode

Hi
How to psubscribe or punsubscribe the topic?
I attempt extends RedisCluster like the next.
	public void psubscribe(final JedisPubSub jedisPubSub, final String pattern, String key){
		new JedisClusterCommand<Void>(getConnectionHandler(), suMaxRedirections) {

			@Override
			public Void execute(Jedis connection) {
				connection.psubscribe(jedisPubSub, pattern);
				return null;
			}

		}.run(key);

	}

	public void punsubscribe(final JedisPubSub jedisPubSub, final String pattern, String key){
		new JedisClusterCommand<Void>(getConnectionHandler(), suMaxRedirections) {

			@Override
			public Void execute(Jedis connection) {
				jedisPubSub.punsubscribe(pattern);
				return null;
			}

		}.run(key);
	}

But I found the way was not perfect. Beacause punsubscribe must use jedisPubSub object, so I must store jedisPubSub in other place...
What is the right way? please help me!

@wanggit Here's an example about the two ways of unsubscribing from a PubSub using Jedis / Jedis cluster

public static void main(String[] args) throws Exception {

      JedisPubSub jps= new JedisPubSub() {
          @Override
          public void onPSubscribe(String pattern, int subscribedChannels) {
              // Subscribed
          }

          @Override
          public void onPMessage(String pattern, String channel, String message) {
              // Message arrived

              if (true) {
                  // You can unsubscribe here due to some condition.
                  unsubscribe();
              }

          }
      };

      Set<HostAndPort> host = new HashSet<HostAndPort>();
      JedisCluster jc = new JedisCluster(host);

      jc.psubscribe(jps, "some pattern");

      // Unsubscribed from here.
      jps.unsubscribe();

  }

This has always been like this in Jedis, so it's not specific to JedisCluster. Basically you need to either:

Keep a reference to the JedisPubSub instance and unsubscribe from there
Call unsubscribe within any of the overridden JedisPubSub methods.

Thanks


Hosts editor wants to merge "duplicate" entries but it should not.

Microsoft PowerToys version
0.68.1
Installation method
Chocolatey
Running as admin
Yes
Area(s) with issue?
Hosts File Editor
Steps to reproduce
Create an entry with more than 9 hosts: 10th and later are not seen by Windows
Split the entry into several not containing more than 9 hosts: Hosts editor warns about duplicate entries
✔ Expected Behavior
No warning for duplicate entries.
❌ Actual Behavior
Warns about duplicate entries.
Other Software
No response

Additionally, it should check that no more than 9 hosts are present per entry.

Fixed in 0.71 release of PowerToys. aka.ms/installpowertoys

Hi @stecydube
Can you please share an example of wrong duplicate entries?

For me it is docker connections:

Exactly that. However in this case it can be argued that it could be merged on the same line.
Not quite so for those lines where they have more than the max of 9 allowed.
So, let's say you have an IP address with 15 entries. They would be split into two lines.
In that case, the yellow triangle should not show, or even better display the two lists under the same address line but keep the resulting text "output" as two separate entries.


Removing dead code with purify-css

(Note: This is a suggestion, not a bug.)
I use several CSS libraries in my code, including Font Awesome and Twitter Bootstrap, which often add a lot of dead weight to my CSS file. I have also been trying to improve loading speed, and the extra CSS code contributes to render-blocking. I found purify-css and purifycss-webpack which search through SPAs for all used classes and remove unused classes from the emitted CSS. They even work well with dynamic className attributes.
My Implementation:
var PurifyCSSPlugin = require('purifycss-webpack');
var glob = require('glob-all');

// Webpack plugin list

new PurifyCSSPlugin({
  minimize: true,
  purifyOptions: { // Animations used by an external library
    whitelist: ['*-leave*', '*-leave-active*', '*-enter*', '*-enter-active*']
  },
  paths: glob.sync([
    path.join(__dirname, './../src/**/*.js')
  ]),
})

I cut my CSS file to less than half by getting rid of all of the features I wasn't using. It would be awesome if this could be implemented by default (or something similar).

I really like to bend and trim down my bundle as much as possible, just not sure this is the best solution for CRA. Given that CRA is "zero conf" how would white-listening work for everyone?
code splitting is coming to webpack https://github.com/webpack-contrib/mini-css-extract-plugin  which will replace extract text plugin later this year and I think its a better approach of cutting down initial resources, although it wont eliminate unused 3rd party library classes.

That makes sense -- you can't anticipate every 3rd party library. And if CRA is transitioning off of the dependency for purifycss-webpack then it's probably better to leave it out altogether.

Or just leave a global variable for whitelisting... I don't know, something like an env entry or so...


TypeError with Strapi v.4.3.3 and v.4.3.4

I got the following client error using the preview button plugin (0.3.6) with strapi v.4.3.3 or v.4.3.4:
TypeError: Cannot read properties of null (reading 'model')
The error occurs when I open a detail view for an entity of a collection type.
plugin config is:
'preview-button': {
    enabled: true,
    config: {
      contentTypes: [
        {
          uid: 'api::article.article',
          targetField: 'slug',
          draft: {
            query: {
              type: 'news',
            },
          },
        },
      ],
    },
 },

Downgrading strapi to 4.3.2. fixes this error, but is not a satisfactory solution in the long run.

Hi @BennyMoser I'm unable to reproduce this issue using Strapi v4.3.4 with the plugin v0.3.6. Your plugin config looks correct. Are you able to share your package.json and any other details about your setup?
This plugin does not reference model anywhere so I'm wondering if it is triggering the error through some mis-configuration.
Also try deleting the yarn.lock and node_modules and running yarn again. (just good to rule it out)

Hi Matt I'm quite familiar with node.js but deleting yarn.lock was the only thing i did'nt try.
And of course it fixes the error. I only deleted the node_modules directory a few times...
Thank you for helping me!


Documentation Still on CodePlex with Many Broken Links

Steps to reproduce
Several links on the main GitHub page
https://github.com/DotSpatial/DotSpatial
redirects the user back to CodePlex where you were just directed to GitHub.
On these old CodePlex pages like the documentation pages
https://dotspatial.codeplex.com/wikipage?title=DotSpatial Tutorials&referringTitle=Documentation
many links are broken, e. g. a download of the tutorial files is not possible anymore.
Expected behaviour
Documentation is moved to GitHub Wiki and links are fixed.
Actual behaviour
User is directed back to CodePlex and many links a broken.

We have time till  December 15th, 2017.
https://blogs.msdn.microsoft.com/bharry/2017/03/31/shutting-down-codeplex/

dead links were removed by #1471


Service for uploading the report PDFs in Hidora, with metdata

@catilgan please review the PR

@dev-ng I reviewed your PR and merged it into master. Great job!! :-)
As mentioned in PR comment, we could add these features later:

Logging mechanism
Limiting the number of extracted PDFs


can u provide more information about how to prepare data for triplet loss?

Any one know how to prepare data for triplet loss?

I have a same question here. Can @xlvector kindly provide some tutorial steps about this? :-)

I think it is just the cifar 10 data set.

I think it's not cifair 10 data set. It should be a directory consist of a few .npy files.

Hey does any one know how to create the npy files frome an existing image dataset ?


Replace video

Following up on #412 , I've updated the video to remove the issues steps, as well as the "STEP BLANKS" transitions.
Looking for a quick 👍 or two from @github/services-training on the changes 😄

@hollenberry This could be just because of my internet connection, but some of the images are pretty fuzzy. Is anyone else seeing this?

Also, there's a slight drop in audio at 2:17 but I don't know if that's a blocker.
Thank you for opening the PR and re-editing to get this updated! 👍

@brianamarie Awesome, thank you for watching!
I think that the quality is due to your internet, as I'm not seeing the same. However, that audio dip is definitely a thing. I wonder if I can easily equalize.

This could be just because of my internet connection, but some of the images are pretty fuzzy. Is anyone else seeing this?

@brianamarie it looked ok in mine but it was playing in HD mode! I'm not sure if there is anything we can do about the compression since YouTube does this automagically - but maybe @loranallensmith  can give us a hint?

compression since YouTube does this automagically - but maybe @loranallensmith can give us a hint?

@crichID I believe @loranallensmith is OOO for the holidays, but I followed this resource for the best practices in exporting/uploading.

@hollenberry I think this video looks :sparkles: in HD but agree it could use a little tweaking for people viewing it in a lower resolution. However, I don't think this should prevent us from shipping this iteration as it will be an awesome resource for our learners. I am going to go ahead and merge this in so I can update the course on services.github.com!
Perhaps after the holidays we could spend some time with @loranallensmith or @pamboat for guidance on tweaks that will make this even better!


com.apple.CallKit.error.requesttransaction error 1

HI.
Thank you for a good job with the example.
However it fails for me on simulator,  when I click on "Start call" with error message , like in the issue title.
I've changed url to mine. Also I've set a breakpoint in GetAccessToken but app never reaches it.
I've also changed bundle id to mine and Automatic Provisioning is selected. Any ideas what is going on?
Voice Over IP is enabled in Background Modes.
Simulated device is iPhone 11 on ios 15.2
Regards

OK, this issue is not present on a physycal device.


Updated kafka-clients version

Short description outlining key changes/additions
Updated version of kafka-clients
JIRA Ticket Number
IDVA6-1484
Type of change

[x] Bug fix
[ ] New feature
[x] Breaking change
[x] Infrastructure change

Pull request checklist

[x] I have added unit tests for new code that I have added
[x] I have added/updated functional tests where appropriate
[x] The code follows our coding standards

An exhaustive list of peer review checks can be read here

CI: Security warnings found!


[W5.8][W14-2] Lai Keen Lok

Hey sorry I think you need to do PR to https://github.com/nus-cs2103-AY1819S1/addressbook-level2.


Pass emit to events and make mixins either a function or object.

Recently we've talked about making mixins a function (by convention, not strictly), so instead of:
mixins: [logger]

...prefer:
mixins: [logger()]

This got me thinking about how to simplify mixins.
To me mixins are a no-brainer, but to a newcomer, it might be frustrating how mixins that take options must be a function that returns a function. 🤔
What if we go back to passing emit to events? This would allow us to make mixins either a function that takes some options or just an object.
Instead of passing emit to events, we can try a midway approach, allowing mixins to behave either as a function that returns a function or a function that returns an object.
For example, @okwolf's logger could be changed to the following (since emit is not necessary):
function logger(options) {
  // Initialize...
  return {
    events: {
      action: function(state, actions, action) {
        // ...
      },
      resolve: function(state, actions, result) {
        // ...
      },
      update: function(state, actions, nextState) {
        // ...
      }
    }
  }
}

And if you want emit, then use it as usual (no API break).
Pros

Allow mixins to be simple objects.
Make mixins that don't use emit simpler to write.
No API break.

Cons

Mixins can take more shapes now. All of the following are valid mixins:

// Basic free plan
const a = {
  events: {
    load() {
      console.log("ok")
    }
  }
}

// Basic free plan with options

function a(options) {
  return {
    events: {
      load() {
        console.log("ok")
      }
    }
  }
}

// Premium plan with emit

function a(emit) {
  return {
    events: {
      load() {
        console.log("ok")
      }
    }
  }
}

// Premium plan with emit & options
function a(options) {
  return function(emit) {
    return {
      events: {
        load() {
          console.log("ok")
        }
      }
    }
  }
}

@jbucaran is this how each of the different "plans" would be used or am I missing something?
// Basic free plan
mixins: [a]

// Basic free plan with options
mixins: [a(options)]

// Premium plan with emit
mixins: [a]

// Premium plan with emit & options
mixins: [a(options]

@okwolf Could there be confusion/errors from a user passing in a mixin function that took options and returned a mixin object VS a mixin function that takes emit and returns a mixin object?

Not sure. But  probably yes, there could be.

to a newcomer, it might be frustrating how mixins that take options must be a function that returns a function. :thinking:

Anyone diving into an Elm-like architecture will sooner or later have to deal with higher-order functions. With proper documentation and good explanations, I don't think that this should be an issue.

https://github.com/hyperapp/hyperapp/commit/5b4a705df02595dd6b6a28bcdb205a1ab530b37e
Thank you everyone for your input.


✨ [Feature] facades.Schedule() supports scale horizontally

Before feedback (在反馈之前)

[X] There are no features that I want to submit in Issues (当前 Issues 中没有我将要提交的新功能)

Describe Feature (描述功能)
To ensure the job is not done two times on multiple same applications. We may need to block other applications by Redis.

English document: https://laravel.com/docs/10.x/scheduling#running-tasks-on-one-server


Update to latest Minio release and add downward API support

Bump to latest Minio release
Added downward API support

@k8s-bot ok to test


Better discord commands

A few small fixes / changes which weren't relevant to guild event messages and will improve the discord side:

Fixed help message timestamp to show current time instead of time since bot was turned on
Delete the !help message alongside the embed once the timer expires
Renamed override to execute as it's a much more logical name
Added unmute command
Commands can be used in any channel the bot can see (application tickets, bot command channels etc)
Promote/Demote commands replaced with Setrank

Thanks for the PR and all the changes, however, there are a lot of unrelated changes that don't seem to belong together in a single PR. Right now the PR adds new commands, delete existing commands, modifies exiting commands, and changes the entire command system to allow commands to be used globally throughout the entire Discord server, all of those changes should really have been individual PRs, otherwise, the commit log just gets muddled with commit messages that don't accurately describe what is actually happening in the codebase.
On the note of using commands globally everywhere, it was a conscious discussion to not allow the bot commands to be used outside of the channel the bot is linked with since most servers using the bridge bot will also have other bots in their server, and the command prefix might conflict with the other bots, if the system is changed so commands can be used throughout the entire Discord server the system would have to be configurable, so people self-hosting the bot can choose to turn it on or off.


update the pizza party tutorial to include how to make a service account

Notes from Aubrrey:
ADDITIONAL STEPS:
In the Developers Console, where you created a Public API access key for your fusion table, click the Create new Client ID button. Select the Service account option, and click Create Client ID.
A file called the KeyFile (ends in extension .p12) will automatically download onto your computer. Save it in a place you will remember. Once the creation is complete, you will get a table with your Service Account information.  creates a  address.
Add the ServiceAccountEmail (from the table on the developers console) and upload the KeyFile to the fusion tables control in the designer window of App Inventor, and check the UseServiceAuthentication box.

SHARE the fusion table with your ServiceAccountEmail (from the table), and give it editing permissions, just like you would share any other Google Doc with an email address.

ALSO, please note that if your column names in the fusion table have spaces between the words, you will need to put single quotes around the column name in your query string.

Aubrey did this


Fix Maven coordinates in README

Summary
Fix Maven coordinates in README
Description
As per the link above the text blob in README.md, https://search.maven.org/search?q=g:software.amazon.jdbc, the group ID is software.amazon.jdbc.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Thank you for catching this.


Reilly refactor

Sync up .pylintrc with bfasst project.
Full refactor of create_data.py
Full refactor of create_libs.py
Refactor compare_v.py and use new functions in create_data.py and create_libs.py
Start of refactor for search_lib.py, located in the file search_lib_refactor.py
Some very basic unittest code, just some framework to get it going

Also, sorry I changed permissions on some files and so they got marked as changed, but the text content is the same


Homebridge not appearing a process in macOS running under node process

Pre Steps
Have installed Node and Homebridge with no problems as per the tutorial, been using Homebridge for a few years now so fairly well acquainted with it. I've tried to Homebridge as a launchdaemon so it's always running even when not logged in on the computer (which is rare, but after a reboot might happen) - it actually works but as a number of weird errors about the setup
Previously Homebridge would always appear in Activity Monitor as it's own process, so you could check it was live and terminate it if required. Now doing ps aux | grep homebridge in Terminal show us a Homebridge process and PID but when you check in Activity Monitor it's actually running as Node.
For some reason I cannot unload or reload the LaunchDaemon script - macOS says it is disabled or doesn't exist (when it does) and I cannot restart Homebridge, it's now always running  within the Node wrapper as Root.
This has knock on problems, the Homebridge Gui doesn't think Homebridge is running because the process doesn't exist.
I also don't appear to be able to stop and start Homebridge.
Versions

Homebridge: 0.4.49
Node:  v12.1.0
OS:  macOS Mojave 10.14.5 (18F132)

This could be a node issue? Even when I manually run Homebridge in terminal, if I check activity monitor it's running as "node" process (in fact two node processes run, one might be the Homebridge Gui-X) - i've not seen this before, I assume it's a recent change...it's as if all processes are running in wrappers.


Flickering LEDs are back.

Version
alpha5
What is the issue?
These are LEDs on the Left Hand End under the 'C' label.
Looks like a retro step as all was well with 4g.
https://github.com/user-attachments/assets/8d77b9f2-49b6-4f30-bab1-952cadc8f248

I think this has been fixed in alpha5.1.A

Does rather look like the DMA quirk is back Fred had earlier.

If you reset your settings on install of the new firmware I believe the default is 40 for noise floor. I can make the lower limit higher for roll over… or assign it to a sub menu so it allows up and down so there is no roll over. 5.1.a does fix it I believe. The buffer function is still the same. I plan on improving it. What I did find, was the strummer1 was always active and cycling and it was lagging down the led timing.
I have now made it so the strummer isn’t activated until a button with strum is pressed and is deactivated after a press. I’m sure I can optimize the strummer a bit to not make it as resource intensive later.

… and closed

I also found that strummer 2 and strummer 3 modules were continually looking to make sure there were no unresolved strum notes to turn off, robbing the chip of thousands of clock cycles per midi pulse. 5.2 has this fixed and should further reduce any of these erroneous pulses being presented.


Numpy 1.12 is not supported

Don't upgrade Numpy to 1.12. The behavior of indexing is changed in 1.12. Unittests failed. I am working on fixing the issue. More details will be added regarding the issue.

Wait I did do the upgrade already, what do you mean exactly?

On 16 Mar 2017, at 14:25, Zhenwen Dai<EMAIL_ADDRESS>wrote:
Don't upgrade Numpy to 1.12. The behavior of indexing is changed in 1.12. Test cases failed. I am working on fixing the issue. More details will be added regarding the issue.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/SheffieldML/GPy/issues/490, or mute the thread https://github.com/notifications/unsubscribe-auth/ABfcKV37b-fALJqnE3rE1ukUio1TOjO2ks5rmUZagaJpZM4MfYBw.

I think you should pull before trying to edit stuff

Thanks for fixes.
Our internal repo was not very up-to-date. We are working on some improvement like for EP code and push to github after some internal approval. I will improve on synchronization.


Missing geostyler as an input parser format

Currently, the client does not support a geostyler file as an input to convert to another format.
Suggested change would allow:
geostyler -s geostyler -t sld -o point_simple.sld testdata/point_simple.geostyler

If no source parser is specified we can also default to "geostyler" and attempt to parse with this.

:tada: This issue has been resolved in version 4.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Issue reporter should try to make people check "reproducible when extensions are disabled"

Issue Type: Feature Request
As the title suggests. Currently there is nothing that urshes you to try checking disabling all extensions before submitting an issue. I suggest showing a warning sign near "Preview on GitHub" when this is not checked.
VS Code version: Code - Insiders 1.21.0-insider (a903bd38fbe9006c076d218ff69fe1ee0160f815, 2018-03-06T10:59:55.398Z)
OS version: Darwin x64 17.3.0

Closing this out as that checkbox no longer exists


ZeroDivisionError in holoviews display

As mentioned in https://github.com/XENONnT/straxen/issues/48#issuecomment-580681218, you currently get a ZeroDivisionError when trying to use the holoviews display. We should post the full error trace here and then try to figure out what (upstream?) change caused this to appear.

Let us know what we (HoloViz developers) can do to help debug this.

@philippjfr Thank you! It appears that this problem has resolved itself: after some updates in our environment we do not see this anymore and our holoviews display works again. Perhaps it was a particular combination of versions that caused this; if we see it again, we'll reopen and try to track it down.


Remove sensor examples, use Grove package

The Grove examples should be removed from the examples directory, these are now in the Grove package.

Fixed in release 1.1


[xaudio2redist] Add new port

Adds a vcpkg port for the NuGet package Microsoft.XAudio2.Redist. This provides XAudio 2.9 in a form you can use on Windows 7 SP1, Windows 8.0, Windows 8.1, and Windows 10.
It does not support UWP or ARM/ARM64. You can use XAudio2.9 directly in those scenarios.

None of the lib or dll names collide with the Windows SDK. The headers do, but they are in a include/xaudio2redist folder.

No idea what the OSX failures have to do with this port...

@walbourn, it's not relate to your changes, it failed with 'no space left in pipeline machine', I have rerun the PR.

OK. I've rebased against the latest master...

cool, thanks @walbourn :)


Gradle Enterprise Trial

This branch is following along with the Gradle Enterprise trial.
Keeping it in draft mode for now, but ideally, we will have a mergeable PR in the end, improving our GE integration and overall Gradle build.

We finished the trial and this could get merged to master now. Completely replaces our S3 cache with the Gradle Enterprise cache. This will also get us rid of the S3 cache exception in the logs for local builds.


Main Page broken link.

On the main page in the A Simple Component section, the Babel REPL text links to https://babeljs.io/repl/#?presets=react&code_lz=MYewdgzgLgBApgGzgWzmWBeGAeAFgRgD4AJRBEAGhgHcQAnBAEwEJsB6AwgbgChRJY_KAEMAlmDh0YWRiGABXVOgB0AczhQAokiVQAQgE8AkowAUAcjogQUcwEpeAJTjDgUACIB5ALLK6aRklTRBQ0KCohMQk6Bx4gA which returns a 404.

From what I can tell, the link redirects to https://babeljs.io/repl/#?presets=reac ... instead of https://babeljs.io/repl#?presets=reac ....

Does this still happen to you? Both the link on the main page and the one you posted here work for me.

Also, It's working for me

Still not working for me:
https://user-images.githubusercontent.com/24500411/103430419-bd5bc980-4b78-11eb-9356-a4b381ac833a.mp4

It's working as expected.
https://user-images.githubusercontent.com/25402167/103456421-1e6fd280-4d1c-11eb-8f24-9a782c767f03.mp4

It's working as expected.
https://user-images.githubusercontent.com/25402167/103456421-1e6fd280-4d1c-11eb-8f24-9a782c767f03.mp4

Closing since this is most likely network related. Maybe some corporate firewall or proxy that's interfering?

Closing since this is most likely network related. Maybe some corporate firewall or proxy that's interfering?


fix: http mock redefinitions always working

Circular map for registry is now properly handled by removing and adding back redefinitions of existing mocks to keep clientId in registry

Codecov Report

Merging #122 (1929689) into main (4587644) will increase coverage by 0.18%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##               main     #122      +/-   ##
============================================
+ Coverage     85.78%   85.96%   +0.18%
  Complexity       35       35
============================================
  Files            31       31
  Lines          2553     2544       -9
  Branches        281      280       -1
============================================
- Hits           2190     2187       -3
+ Misses          246      240       -6
  Partials        117      117

Impacted Files
Coverage Δ

.../java/com/decathlon/tzatziki/utils/MockFaster.java
83.33% <100.00%> (+1.74%)
:arrow_up:

.../main/java/com/decathlon/tzatziki/utils/Types.java
63.82% <0.00%> (+2.12%)
:arrow_up:

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


Resetting throttle count between tests

Just wondering, what is the best way to reset the rack attack counters between "it" blocks in a spec, so that throttling can be tested independently in different "it" blocks.
I presume one would use an around block like this...
        around(:each) do |each|
            clear_rack_attack_cache
            each.run
            clear_rack_attack_cache
        end

Then perhaps...
        def clear_rack_attack_cache
            while Rack::Attack.cache.store.instance_variable_get(:@data).keys.length > 0
                Rack::Attack.cache.store.clear
                sleep(1)
            end
        end

FYI, using ActiveSupport::Cache::MemoryStore as the backing store. Is a sleep required or is this synchronous?
Either way, it doesn't seem to be working quite right for me as I don't always get the expected number of 200's before I get a 429.

I'm doing this, it seems to work...
    Rack::Attack.throttles.each do |k, throttle|
      Rack::Attack.cache.reset_count("#{k}:#{key}", throttle.period)
    end

For the record,

It appears to me that Rack::Attack.clear! is a bit confusing in that is resetting some things, not everything.

clear! has been renamed to clear_configuration to avoid further confusion in https://github.com/kickstarter/rack-attack/pull/344.

think this is something we should add explicit support for, so users don't need to hack the cache store in order to achieve test case isolation in their app tests.

Issue with this goal is the following https://github.com/kickstarter/rack-attack/issues/301

We should consider adding a Rack::Attack.reset! method, which should reset all Rack::Attack-specific state (mostly throttles, fail2ban and allow2ban counters) so that users can for example do something like:
config.before do
  Rack::Attack.reset!
end

when using RSpec.

We should consider adding a Rack::Attack.reset! method, which should reset all Rack::Attack-specific state (mostly throttles, fail2ban and allow2ban counters) so that users can for example do something like:
config.before do
  Rack::Attack.reset!
end

when using RSpec.

Rack::Attack.reset! has been implemented and merged in https://github.com/kickstarter/rack-attack/pull/436.


OCMockObject invocations retain arguments

OCMockObject invocations need to retain their arguments, however that can introduce retain cycles that wouldn't otherwise be there. It also makes dealloc tests fail for objects that get sent as arguments to mocks.
Break the chain in -stopMocking by emptying out the invocations.
https://github.com/erikdoe/ocmock/issues/307

This is based on the suggestion in the issue by @fareal that -stopMocking be used to release arguments to mock objects, and potentially break retain cycles that can result as described by @alexito4.
The gotcha here is that mocks can no longer be verified after -stopMocking has been called. In practice I don't see how that could be an issue, but it is a behavior change that I want to point out up front.
I don't see any great alternatives though.

Add a way to opt-out of the autorelease-safe and thread-safe behavior introduced in #171 a la #348. For people who really know what they're doing and can guarantee that nothing in the invocation will get released for the lifetime of the mock, then ok, but that seems sketchy.
Take @fareal's solution verbatim. The problem with his solution is that -stopMocking would then restore the original problem where the invocations can hold zombies, which can cause crashes. If you don't use the mock after -stopMocking (and it seems to me like you really shouldn't) then it's not a problem. But if you do keep using the mock, probably to verify, it seems better to me to fail the verifies rather than sporadically crash.
Add an explicit method to empty out all of the captured invocations. This would allow verification after -stopMocking, but I don't know if anyone actually wants to do that so I don't know if it's really worth adding another method.
Do nothing. I think the retain cycle problem at least is worth fixing.  There are several related issues/complaints here that would seem to prove that. So I think it's worth making those possible too.

So I think the behavior change is worth it on principle, and I think it will make more people happy than it makes angry?

I think this proposal is fine on the face of it. -stopMocking IMO is essentially tearDown for the mock. But using it afterwards should fail aggressively with appropriate warnings / messages.
Would you consider amending your diff to add a fault, maybe NSException, or if we want to be really aggressive a hard coded call to abort() if expect is called on a mock after stopMocking?
Also if I read this right -stopMocking is now a required call for all types of mocks, not just Class or partials?

No, this proposal doesn't make -stopMocking a required call for any mocks where it wasn't already. It just makes it so that -stopMocking can be used to manually release the captured invocations on the mock, rather than relying on the mock's own object lifecycle. This is particularly important when the mock retains objects that the real object normally wouldn't, and the objects it's retaining in turn hold a strong reference to the mock. Prior to this proposal there was no way out of that situation, but with this proposal you can now manually call -stopMocking to break the retain cycle. So I wouldn't say this adds a requirement, but rather it adds an option to fix a previously un-fixable situation.
I'm not opposed to installing a land mine after -stopMocking is called, but I think that should be a separate diff/proposal.

@erikdoe Any updates on this one? It's kind annoying that the arguments were captured after stopMocking is called 😢

It certainly took a very long time for me to merge this. Somehow, against the odds, I was still hoping to find a more elegant solution. I didn't.
After merging this PR I also added the "land mines" mentioned above. If tests try to use the verify after run functions or the mock itself, and exception will be thrown. I thought this was super important because without it, the exception thrown when trying to verify after run after stopMocking would have been very misleading.

Woohoo! Thank you for checking this one out, and also doing the follow up land mines too!


Decouple prison-specific ID requirements from Rails internals

The use of lookup_context is highly dependent on the internal workings of Rails, and makes it hard to upgrade to Rails 4.2.
We replace this with a more explicit method:

Find the template (either specific or generic) on disk
Return its content
Render as Markdown if appropriate, using separate text and HTML templates

Looks good. Merging.

This is great, nice work @threedaymonk! The simplicity of prison_specific_id_requirements in  :boom:


Make telemetry opt-out

Why do we even want telemetry?
The Kedro team uses telemetry to understand product usage and make data-informed decisions that benefit our users. For example, we were able to determine that certain CLI subcommands had very little usage https://github.com/kedro-org/kedro/issues/1293, https://github.com/kedro-org/kedro/issues/3750. The alternatives would have been

Conduct expensive user interviews (that we need to do anyway for more complex issues, hence exhausting our user base), or
Keep those commands around, bloating the project.

Therefore having telemetry is a low-cost way for us to keep improving Kedro for everyone.
What is wrong with the current telemetry collection process?
At the moment the telemetry collection has two layers of opt-in:

kedro-telemetry needs to be installed. At the moment this happens because we're introducing it in the requirements of our starters:

https://github.com/kedro-org/kedro/blob/bf536d4029d94bb318848b150be78d23fca44fb4/kedro/templates/project/{{ cookiecutter.repo_name }}/requirements.txt#L1-L9
However, this significantly skews the data we have. We have anecdotal evidence that many people don't even know what kedro new is, and also teams often have their own templates, starters, ways of working.
In addition, this blocks progress on relocating the optional dependencies of our starters https://github.com/kedro-org/kedro/issues/2519.

The moment kedro-telemetry is installed and certain (not all) Kedro commands are run for the first time, a blocking prompt is presented to the user asking them whether they opt in for telemetry or not. This prompt causes lots of problems in different environments (see https://github.com/kedro-org/kedro/issues/1640). Current workarounds, like creating a .telemetry file ahead of time, are finicky because sometimes it's not obvious what the working directory of the commands are. In these cases we have just told users to pip uninstall kedro-telemetry and go on with their lives, hence losing that information from our side.

Effectively, the presence of this telemetry collection mechanism is both giving us biased data and also actively preventing our users to do their work.
Something has to change.
What do we want to change?
After exploring adjacent libraries and projects as part of https://github.com/kedro-org/kedro-plugins/issues/510#issuecomment-1885237973, we observed that all of them have an opt-out telemetry collection mechanism.
Therefore, we want to converge with the rest of the ecosystem and make Kedro telemetry opt-out as well.
[Waves arms angrily]
We get it. Some developers and users don't like the idea of opt-out telemetry. Defaults matter.
And yet, if we fail to collect such telemetry, we fail to fulfill our goal of continuing to improve Kedro in a cost-effective way, hence all Kedro users are negatively impacted as a result.
As such, we have taken measures in the past few months to reduce the amount of data we collect:

We fixed a bug on how telemetry commands were masked #552
We are not hashing usernames anymore, and instead we rely on UUIDs #596
We are not hashing project names anymore, and instead we salt them with project UUIDs #701

This is reflected in our telemetry collection policy https://docs.kedro.org/en/0.19.6/configuration/telemetry.html and we still fully stand by it:

This data is collected with the sole purpose of improving Kedro by understanding feature usage. Importantly, we do not store personal information about you or sensitive data from your project, and this process is never utilized for marketing or promotional purposes. Participation in this program is optional, and Kedro will continue working as normal if you opt-out.

Therefore we're committed to storing the minimal amount of information possible, have none of that be personal information (not even IP addresses), make Kedro work exactly the same without it, and offer even more ways to opt out.
We also considered that we had to write all this for full transparency with our users.
What's next?
We are looking into ways to make telemetry collection opt-out, which means: it will be enabled by default for all Kedro Framework projects.
This means that, ideally, anyone who does pip install kedro and performs a kedro run ought to see a message like this:
Kedro is sending anonymous usage data with the sole purpose of improving the product. No personal data or IP addresses are stored on our side.
If you want to opt out, set the `KEDRO_DISABLE_TELEMETRY` or `DO_NOT_TRACK` environment variables, or create a  `.telemetry` file in the current working directory with the contents `consent: false`.
Read more at https://docs.kedro.org/en/latest/configuration/telemetry.html

Notice the addition of the KEDRO_DISABLE_TELEMETRY and DO_NOT_TRACK environment variables.

Great write up, and it's the decision I hoped the team would come to for a long time! Excited to see this (hopefully) move forward.

Fully agree with @tynandebold - very happy to see this, and it's a great writeup 👍
Just to understand, the move from hashing username/project name to UUIDs is because it's even more anonymous? Since,  in theory anyway, one could brute-force hashed data to reverse engineer the unhashed username?

Just to understand, the move from hashing username/project name to UUIDs is because it's even more anonymous? Since, in theory anyway, one could brute-force hashed data to reverse engineer the unhashed username?

Correct. Our hash function is public and fast, so potentially the data is vulnerable to dictionary attacks.

Great summary and proposal, @astrojuanlu! I fully agree that telemetry should be integrated into Kedro, rather than being a standalone library. Additionally, I want to point out that telemetry is currently not working with the kedro new command. I believe the new consent system should address this issue, when commands are executed outside of a Kedro project folder.

Notice the addition of the KEDRO_DISABLE_TELEMETRY and DO_NOT_TRACK environment variables

What's the purpose of each of these environment variables? Can't we just add 1?

DO_NOT_TRACK is an attempt at standardising a single environment variable name that many tools could adopt, so that end users don't have to opt out of each and every one of them https://consoledonottrack.com/. It's inspired by the W3C Tracking Preference Expression https://www.w3.org/TR/tracking-dnt/
On the other hand, there might be people that care specifically about Kedro telemetry, or might choose the explicit setting for whatever reason, hence having KEDRO_DISABLE_TELEMETRY is also needed.
Inspiration:

https://github.com/vercel/turbo/pull/6743

This is totally optional, completely anonymous, and can be disabled via CLI (turbo telemetry disable), or multiple environment variables (DO_NOT_TRACK=1 or TURBO_TELEMETRY_DISABLED=1.

https://github.com/tilt-dev/tilt/pull/2878/

Either TILT_DISABLE_ANALYTICS or DO_NOT_TRACK.

https://github.com/netdata/netdata/pull/7846

Either DO_NOT_TRACK=1 or a custom --disable-telemetry flag.

Is there anything left to do for this ticket?  @astrojuanlu @DimedS

I believe the viz telemetry update mentioned in the ticket above is currently in viz's inbox. Additionally, if time permits, we should consider adding more integration tests: https://github.com/kedro-org/kedro-plugins/issues/770. Also, this telemetry-related ticket is quite important: https://github.com/kedro-org/kedro-plugins/issues/794

YES! 🎉


First class telemetry filter config

Proposal: https://docs.google.com/document/d/1f_emnIfPX3i_rLFzNYmUQvsKxuUknXWv_qJZ3RYBn9U/edit#
Work items:

[ ] Implement HTTP metadata exchange in istiod
[ ] Implement TCP metadata exchange in istiod
[ ] Implement Prometheus filter in istiod
[ ] Implement Stackdriver filter in istiod
[ ] Implement Access log policy filter in istiod

When we do this we should consider what does and doesn't make sense as a plug-in. In my opinion the old plugin logic was very complex and led to many bugs and hard to understand behavior. It's slightly better now but still wrong - plugins take in more info than they require which leads to a lot of missing/fake data passed at various call sites

When we do this we should consider what does and doesn't make sense as a plug-in. In my opinion the old plugin logic was very complex and led to many bugs and hard to understand behavior. It's slightly better now but still wrong - plugins take in more info than they require which leads to a lot of missing/fake data passed at various call sites

I will try to clean up those existing tedious, error-prone or fake data. Yes, I agree, the existing plugin codebase for AuthN/Z is pretty complex, and probably I would make it simplified while i'm working on this project.

we should consider what does and doesn't make sense as a plug-in. In my opinion the old plugin logic was very complex and led to many bugs and hard to understand behavior.

Is plugin logic intrinsically complicated, or writing them as a plugin make them unnecessarily complicated? If it is the former, wouldn't it be more problematic if they are implemented in core?

@bianpengyuan part of the problem was that it was a huge leaky abstraction. The plugin params took in like 15 fields, so call sites would only pass some subset to them because they knew the function they called happened to only use those fields.
This has been trimmed a bit (part of it was post-mixer cleanup) but it's not great.
There is also some awkward parts like OnInboundFilterChain. I am pretty sure that would be more clear written a different way (maybe plugin concept is fine, but a different entry point?) for example.
Anyhow, I am not sure that plugin is wrong - I am just not sure it's right either, so we should look into changing it if it makes sense.
cc @yangminzhu if you have any input here

I made some progress there by implementing the httpmx plugin and tested the code, it works. I did not use that much complex logic used in the AuthN, I just constructed a httpmx filter via the Wasm API . I think the workflow there is correct, but definitely it can be simplified. Since I think some logic in building filterchain and building listeners part might be overlapping or unnecessary. So I vote the first, plugin logic is intrinsically complicated but can be simplified.

To more directly answer, the plugin logic is probably pretty complex but it's "essential complexity". I am more concerned about the accidental complexity of the plugin interface.
If we want the minimal change it would probably be reasonable to split the Plugin params so each method can take in different, smaller scoped, inputs.

To more directly answer, the plugin logic is probably pretty complex but it's "essential complexity". I am more concerned about the accidental complexity of the plugin interface.
If we want the minimal change it would probably be reasonable to split the Plugin params so each method can take in different, smaller scoped, inputs.

Yes, I think we can do that depend on the usages of the plugin, which kind of filters we want to build and insert in the envoy config_dump. But that definitely need a little bit redesign. Not sure if @yangminzhu want to put effort there.

If we'd do it again, we'd probably structure it as an xDS proxy without actual wire bits. I think it might help to think in those terms. We could provide additional decorators by some sort of map[proto.Message]InputInfos associated with it.


Support custom key file names with ssl connections

Start-SshAgent finds all keyfiles (standard and cusomt named) and passes their paths to Add-SshKey.

Might make more sense in Add-SshKey?
The pageant logic searches for all .ppk files in ~/.ssh if no files are provided to Add-SshKey, this could do the same thing rather than just letting ssh-add load the files it looks for by default.

On the flip side, I can see value in aligning Add-SshKey with ssh-add's no-arg behavior.
What if there were an -All option?

Add-SshKey - default ssh-add
Add-SshKey -All - all keys in ~/.ssh
Add-SshKey [-File] 'list','of','files' - specific paths

From a single-responsibility standpoint, would it make sense to remove the Add-SshKey call from Start-SshAgent to be more explicit about what key(s) should be loaded?

Removing the Add-SshKey call makes sense, putting it separately into the profile would make it more obviously user-configurable, which would work well with the -All option. Plus, it'd be more accurate naming, since the function is Start-SshAgent rather than Start-SshAgentAndAddKeys. Seems like a good idea.

Just one more thought on the single-responsibility approach: I think leaving out Add-SshKey from Start-SshAgent would over do it. The SSH-Agent is rather useless without any key associated with it. I agree with you on the changes proposed to Add-SshKey, but I think that Start-SshAgent should also take a [-File] 'list', 'of', 'Files' parameter, potentially with an -All option. This way the API would ensure that the SSH Agent is started in a usable way by reminding the developer that keys are actually required to make the connection happen. What's your take on this?

I agree that it's rather useless without an add, but I'm not sure the happy path user is really impacted if we change the default profile to Start-SshAgent; Add-SshKey. Seems simpler than mirroring Add-SshAgent parameters onto Start-SshAgent?

I'll do both, then you can review and select the one you like better.
Should I also add an option to use a different path to hold the keys? I was thinking something along the lines Add-SshKey [-File] 'list', 'of', 'files' -All -Path 'Custom/KeyFile/Path', where -Path defaults to "$env:USERPROFILE/.ssh". Same would go for the extended version of Start-SshAgent.
I'll start with the other changes while waiting for your feedback.

I think I'm fine with the extra parameters on Start-SshAgent. It's not like these will really ever be used outside a profile. (Please correct me if this is an invalid assumption!)
Adding -Path seems reasonable. Or we could make sure absolute file paths can work, ideally from pipeline (e.g. gci C:\my-ssh | Add-SshKey)? Or both, I suppose? Thoughts?

The -File already takes any kind of path and subsequently passes it to the SSH agent being used. It's the -All that currently implicitly assumes that the key-files reside in $home/.ssh/. The -Path would allow to specify a different path being used for providing the key-files for both, -File and -All. So for -File one could then either pass in the FullName, or just the file name. In terms of precedence I'd suggest to consider -Path as the default, which can be overriden by providing a FullName to -File, e.g.:`

Add-SshKey 'I:/dont/like/folders/starting/with/fullstop/myKey', "$home/.ssh/id_rsa" (already works)
Add-SshKey -All (already works, assuming keys reside in $home/.ssh)
Add-SshKey 'I:/dont/like/folders/starting/with/fullstop/myKey', 'id_rsa' (would work with -Path defaulting to $home/.ssh)
Add-SshKey -Path 'I:/dont/like/folders/starting/with/fullstop' -All (would use all keys residing in I:/dont/like/folders/starting/with/fullstop)

Same of course works for pageant using .ppk.
I don't know if it's ever going to be used, but it struck me as an inconsistency in the API of one single commandlet. If you think that I should implement it, I'd propose to also make this available via Start-SshAgent by adding a -KeyPath parameter. Or maybe call it -SshDirectory?

And yes, I need to verify that piping path strings works as well ;)

In terms of precedence I'd suggest to consider -Path as the default, which can be overriden by providing a FullName to -File...

You're spot on. Make it so!
-Path seems sufficient. Probably not much effort to support Add-SshKey -All -Path 'C:/ssh1','C:/ssh2', too?


Can we view Matching tags in filtered streams please?

Matching rules
When an activity is delivered through your filtered stream connection, in a matching_rules array, it contains which list of filters matched against the Tweet delivered.

Also needing this. All we got right now is the data field.

I've implemented this in a fork https://github.com/vilanz/go-twitter. Trying to find a way to make it not be a breaking change, will create a PR afterwards.


I can not connect to postgresql in superset

postgresql is a docker container
postgresql version 13.0
superset is a docker container
superset tag is latest
when i use superset create a database to test connect a postgresql container   it  says Connection looks good!
Then i click the add   it  says An error occurred while creating databases: Connection failed, please check your connection settings
this is my url to connect postgresql  postgresql+psycopg2://admin:admin@{IP}:{PORT}/{MY_DB}

Hi @Geek-sky can you share logs from both Docker containers so community members can attempt to debug? It's tough to help you without the full picture and context :(
I'd also recommend posting to Stack Overflow using the apache-superset tag

I just resolved my problem with nothing
Sorry to brother you all @srinify


Update 130.1-fourier-transform-drawing.md

Wonderful Challenge. I have learned a lot. Thank you so much!

Thanks for this ❤

Than you! :)
Carlos Ponce

On Feb 6, 2019, at 5:31 AM, Nico Finkernagel<EMAIL_ADDRESS>wrote:
Thanks for this ❤
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Plugin not supports field reservation

Create a proto file and paste

syntax = "proto3";

message Test{
    reserved 2;
    reserved "to_be_reserved";

    int32 field = 1;
    int32 to_be_reserved = 3;
}

The plugin doesn't recognize field reservations (as mentioned in language guide https://protobuf.dev/programming-guides/proto3/#fieldreserved)

Currently we support those symbol:
syntax = "proto3";

message Test{
    reserved 2;
    reserved to_be_reserved;

    int32 field = 1;
    int32 to_be_reserved = 3;
}

I will update the AST to support this.

Will be resolved in 2.0.0, currently we are running 2.0.0-EAP, you can join us to test it.


feat: Semantic release automation

Description

Rename release.yaml to build-image.yaml
Use semantic releaser action to create github releases/tags automagically. (Also note that this has cut over to the beta branch for as the default branch)

What type of PR is this? (check all applicable)

[x] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Related Tickets & Documents
Closes https://github.com/open-sauced/pizza/issues/40
Mobile & Desktop Screenshots/Recordings
N/a
Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
👀 have to keep an eye on this and make sure it works as intended!
[optional] What gif best describes this PR or how it makes you feel?


Normal and Hard mode scores are not currently stored separately for jubeat

I'm working on getting jubeat festo support in this server and have had quite the ride learning how this server works and I was curious as to how I should approach storing hard mode scores. I was thinking to just create a new table for hard mode scores and when a given song only has a score in hard mode i make a blank entry in the normal mode score table so that I only need to iterate once through the table and check both tables for a score. I would prefer not to make a second table but since all the scores are currently uniquely stored in the table I couldn't think of any other reasonable approach

Are hard mode scores newly introduced in Jubeat? I don't remember there being any separation of scores except by song/chart. Your proposed method is a bit hacky, there's a reason why there isn't any game-specific tables in the server. Do you have a reference or a quick description for hard mode versus normal mode in Festo?

When the game sends back a score, there is now an is_hard_mode variable sent back and when the server sends the scores to the game there is now two blocks sent per song id, one for hard mode and one for normal. I'm not sure if this is done before festo because I didn't look too much into clan.

Remywiki links to https://twitter.com/jubeat_staff/status/1017392642030571521 which says that yes, this was added for festo. In order for front-end support to kinda "drop in" for hard mode charts, you will definitely want to support these in a more standard way. I can't think of any other games that store separate scores for normal and hard mode except for maybe oooold Pop'n (even IIDX just stores the clear lamp achieved on the hardest mode, while keeping the scores identical).
This network software purposefully keeps a separation between in-game song/chart and its own concept of song/chart. This has made it easy to link songs through ID renames (thanks DDR), revivals (thanks IIDX) and even shuffling around chart ID (thanks Pop'n). You can see this most clearly in Pop'n 19 where they added Cho mode which adds cools. I linked those charts to the standard easy/normal/hard/ex charts in newer Pop'n games so the scores can be forwards compatible. I think the solution is to do a similar thing here. Let's define a new set of charts for hard mode easy, normal and ex, add those charts as well as the normal charts in read.py (they will be duplicates with different chart IDs which is fine), and then in the festo backend we can convert from game song/chart to the correct backend song/chart by looking at the is_hard_mode variable. You'll need to make sure that older versions of games filter out those scores and don't send them back to clients.
We can ignore displaying hard mode scores on the front end for starters until we figure out if we want them there, and if so, how to display them.

I finally got around to working on it again and followed your advice and got it working. I need to get it implemented in webui but thank you so much for your input, it was super helpful.


Insert() returns null on Simple.Data.Mysql on Mono 2.10.8

Mysql => 5.1.44
Simple.Data => <IP_ADDRESS>
Simple.Data.Ado => <IP_ADDRESS>
Simple.Data.Mysql.Myql40 => <IP_ADDRESS>
Mysql.Data => <IP_ADDRESS>
Mono 2.10.8 on Mac 10.6
All obtained from nuget
var db = Database.Open();
var user = db.Users.Insert(name: "abs" , age: 21 );
Insert() returns null
output of show columns in users
+-------------+--------------+------+-----+---------+----------------+
| Field         | Type | Null | Key | Default | Extra |
+-------------+--------------+------+-----+---------+----------------+
| name        | varchar(255) | YES | | NULL | |
| age           | int(11) | YES | | NULL | |
| Id | int(11) | NO | PRI | NULL | auto_increment |
+-------+--------------+------+-----+---------+----------------+
3 rows in set (0.00 sec)
But all works well in Windows.
I think the problem is in In Simple.Data => Extensions/BinderExtensions.cs : line 35
it worked when
ResultDiscardedGetter = ResultDiscardedGetter ?? (_ => true);
is changed to
ResultDiscardedGetter = ResultDiscardedGetter ?? (_ => false);

Should be fixed now, need to build for Mono from latest source.


Retry failed PR merges

Will retry failed merges twice in 15s intervals.

The change LGTM. Add a minor comment.


src: fix linting errors

Mostly added missing semicolons, enforced single quotes, and used strict equality. Also removed the "camelcase" option since it has been deprecated (see http://jshint.com/docs/options/#camelcase).

Tests don't pass for me because this file does not exist but I take it that the tests aren't very comprehensive yet anyways? Also I'm gonna look into making the https cert path part of the config rather than hardcoded.


Add a simple runner for pedagogical purposes.

The existing FnApiRunner has become to complex over the years to serve this purpose.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @hjtran

Run Python_Runners PreCommit


Swift 3.0

@KyoheiG3 LGTM 🍺
when will this be merged?

Hi, @chrisdoc
Merged this pull request.
Thanks.


Adding 2 new applications

Awards and Recognition App
Awards and Recognition Copilot

Both the apps having dependency on Awards and Recognition Base.

@microsoft-github-policy-service agree [company="{your company}"]


add Companys

There should be an additional record that is for Companies:
Name
description
URL

hii, i a can help with that :)

@kentonh Are you talking about a new model?

@jcserracampos maybe model, migrations....perhaps controller..we need more explanations here :)

The end result will be similar to what's happening with Resources, the information will just be slightly different.
Create a new model for Company.
A Company should have:

Name (text)
Logo (via upload or URL)
Website (URL)
Description (text area)

A new nav item should be added, linking to an index view (similar to People index)
Clicking on a single company should present a detail view of the Company record.
Want more?

@kentonh I can do it.

@kentonh Can I take this?
@jcserracampos Did you get a chance to work on this or can I take this and fix it?

You can take.
Em Sex, 14 de out de 2016 2:50 AM, Logesh Mohanasundaram <
<EMAIL_ADDRESS>escreveu:

@kentonh https://github.com/kentonh Can I take this?
@jcserracampos https://github.com/jcserracampos Did you get a chance to
work on this or can I take this and fix it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/StartupWichita/startupwichita.com/issues/14#issuecomment-253715433,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGtmIvcS_kJfeCnqTLjhj2bVRrZq_xHTks5qzxhBgaJpZM4FoWiP
.

--
Júlio Campos
+55 62 9911-1993

Hi @jcserracampos @kentonh
Is there any update on this? If not, I'd like to tackle it.

It's all yours @cesc1989

Good. I'd like you to know I got here following Hacktoberfest tag.

@cesc1989 There's no problem for me.

Hello @kentonh not sure where else to ask so gonna do it here:
I've configured the project in a Vagrant machine. I'd normally do rails s -b <IP_ADDRESS> -p 8000 to start the web server however, instead of webrick it starts a puma server stating: tcp://<IP_ADDRESS>:8000 and I can't access localhost. Any idea why could this be happening?
BTW, I asked because in the gemfile puma gem is under production group.
Thanks.

Never mind :D My Vagrantfile was misconfigured (VSCode gave me the wrong file)

@cesc1989 you have 100% perfect timing, as I was just about to dig into this, you fixed your own issue!

My bad! @kentonh It's taken me a lot more than I thought to start working on this. In a few hours you'll get news on this issue :)


[Bug]: Installation Process Client Name unlimited input box

Make sure your check these beforehand!

[X] Issues - https://github.com/angristan/openvpn-install/issues
[X] README and FAQ - https://github.com/angristan/openvpn-install
[X] Wiki - https://github.com/angristan/openvpn-install/wiki
[X] Discussions - https://github.com/angristan/openvpn-install/discussions

Server OS
Debian 11
OpenVPN version
No response
Client
No response
What is the bug?
When I try to install its showing unlimited client name option. I cant kill this process:

Relevant log output
No response

You need to input the client name with your keyboard :)


libsvm: 3.25 -> 3.31

Description of changes
Updated library to the newest version.
I also cleaned up the derivation by:

Enabling OpenMP
Adding multiple outputs
replacing buildPhase with buildFlags
Replacing postFixup with fixDarwinDylibNames hook

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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.05 Release Notes (or backporting 22.11 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

[x] Fits CONTRIBUTING.md.

Paging @spwhitt as maintainer.

Result of nixpkgs-review pr 221325 run on x86_64-linux 1

2 packages built:

libsvm
saga

Seems to work OK with manual testing.

Result of nixpkgs-review pr 221325 run on aarch64-darwin 1

2 packages failed to build:

libsvm
saga

Build failed on darwin aarch64 due to missing OpenMP header file:
error: builder for '/nix/store/04vv0fm24gyas8s7yali3f3srrksmdrh-libsvm-3.31.drv' failed with exit code 2;
       last 10 log lines:
       > configuring
       > no configure script, doing nothing
       > building
       > build flags: SHELL=/nix/store/ncw57j62jmhsi8l019anl1k8a13g0ykw-bash-5.2-p15/bin/bash lib all
       > clang++ -Wall -Wconversion -O3 -fPIC -fopenmp -c svm.cpp
       > svm.cpp:12:10: fatal error: 'omp.h' file not found
       > #include <omp.h>
       >          ^~~~~~~
       > 1 error generated.
       > make: *** [Makefile:26: svm.o] Error 1
       For full logs, run 'nix log /nix/store/04vv0fm24gyas8s7yali3f3srrksmdrh-libsvm-3.31.drv'.

Result of nixpkgs-review pr 221325 run on x86_64-linux 1

2 packages built:

libsvm
saga


Bugs in Windows Playbook found during regular deployment

TASK [MSVS_2022 : Get SHA256 checksum of the file]

fatal: [build-azure-win2012r2-x64-4]: FAILED! => {"msg": "The conditional check '(vs2022_layout_ready.stat.exists ) and (windows_version.stdout_lines[0] | regex_search('^(10\\.|11\\.|2016|2019|2022)'))' failed. The error was: error while evaluating conditional ((vs2022_layout_ready.stat.exists ) and (windows_version.stdout_lines[0] | regex_search('^(10\\.|11\\.|2016|2019|2022)'))): 'dict object' has no attribute 'stat'\n\nThe error appears to be in '/tmp/awx_2108_g14r8155/project/ansible/playbooks/AdoptOpenJDK_Windows_Playbook/roles/MSVS_2022/tasks/main.yml': line 34, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Get SHA256 checksum of the file\n  ^ here\n"}

Like https://github.com/adoptium/infrastructure/pull/3244 the code for when msvs_2022 is not present needs to be put in its own block to make it easier for ansible to evaluate the when conditions ✅ fixed with https://github.com/adoptium/infrastructure/pull/3248
TASK [MSVS_2022 : Transfer VS2022 Layout File]

changed: [test-azure-win2016-x64-1] => {"changed": true, "checksum": "69f00c74e5634f3834caa4f11e499b2a381c12e4", "dest": "C:\\TEMP\\VS2022_Layout.zip", "failed_when_result": false, "msg": "failed to copy file /Vendor_Files/windows/vs_layout_2022.zip: Unhandled exception while executing module: There is not enough space on the disk.\r\n", "operation": "file_copy", "original_basename": "vs_layout_2022.zip", "size":<PHONE_NUMBER>3, "src": "/Vendor_Files/windows/vs_layout_2022.zip"}

No space left in disk when moving vs_layout_2022.zip onto machine. Affects test-azure-win2016-x64-1, test-azure-win2019-x64-1, build-ibmcloud-win2022-x64-1
TASK [MSVS_2022 : Register Visual Studio Community 2022 DIA SDK shared libraries]

failed: [test-azure-win11-aarch64-1] (item=C:\Program Files\Microsoft Visual Studio\2022\Community\DIA SDK\bin\msdia140.dll) => {"ansible_loop_var": "item", "changed": true, "cmd": "regsvr32 /s \"C:\\Program Files\\Microsoft Visual Studio\\2022\\Community\\DIA SDK\\bin\\msdia140.dll\"", "delta": "0:00:00.262765", "end": "2023-11-09 12:55:40.345830", "item": "C:\\Program Files\\Microsoft Visual Studio\\2022\\Community\\DIA SDK\\bin\\msdia140.dll", "msg": "non-zero return code", "rc": 3, "start": "2023-11-09 12:55:40.083065", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}

Fails to register VS community 2022 libraries ✅ Fixed by manually installing msvs2022 on the machine. It was failing to install due to lack of space, and therefore the directories it is trying to register were not present
TASK [Java_install : Download Java16]

fatal: [build-ibmcloud-win2012r2-x64-2]: FAILED! => {"changed": false, "dest": "C:\\temp\\jdk-16.zip", "elapsed": 0.0470005, "msg": "Error downloading 'https://api.adoptopenjdk.net/v3/binary/latest/16/ga/windows/x64/jdk/hotspot/normal/adoptopenjdk?project=jdk' to 'C:\\temp\\jdk-16.zip': The remote name could not be resolved: 'api.adoptopenjdk.net'", "status_code": null, "url": "https://api.adoptopenjdk.net/v3/binary/latest/16/ga/windows/x64/jdk/hotspot/normal/adoptopenjdk?project=jdk"}

build-ibmcloud-win2012r2-x64-2 is having trouble resolving api.adoptopenjdk.net

Just to note, the install of MSVS2022 takes up quite a bit of space. The transfer of the VS2022_Layout.zip is 13G, when unzipped takes another 15G. The product to be installed is around 20g. The installed and unzipped directory are both removed after the install but during the install if the machine does not have the required space for all three of these things then the task fails

Just to note, the install of MSVS2022 takes up quite a bit of space. The transfer of the VS2022_Layout.zip is 13G, when unzipped takes another 15G. The product to be installed is around 20g. The installed and unzipped directory are both removed after the install but during the install if the machine does not have the required space for all three of these things then the task fails

That sounds like really good information to store somewhere. Maybe we could create a FAQ.md entry to document how much total space is required for a "base" playbook run on different OSs, starting with Windows and "before/after playbook" sizes?
I know it required around 100Gb previously (but of course for build purposes you need more space somewhere for the jenkins workspaces) so it would be good to know if that has gone up now.


Error Multiple devices when only one is attached

Scrcpy recently stopped working for me, I'm getting an error that there are multiple devices but when I run "adb devices" there is only one listed
 $ scrcpy -b2M -m800
2019-08-27 14:20:12.101 scrcpy[59628:611984] INFO: scrcpy 1.10 <https://github.com/Genymobile/scrcpy>
/usr/local/Cellar/scrcpy/1.10/share/scrcpy/scrcpy-server.jar: 1 file pushed. 0.5 MB/s (22662 bytes in 0.045s)
adb: error: more than one device and emulator
2019-08-27 14:20:12.237 scrcpy[59628:611984] ERROR: "adb reverse" returned with value 1
2019-08-27 14:20:12.237 scrcpy[59628:611984] WARN: 'adb reverse' failed, fallback to 'adb forward'
27183
2019-08-27 14:20:12.881 scrcpy[59628:611984] INFO: Initial texture: 800x448
[server] ERROR: Exception on thread Thread[main,5,main]
java.lang.IllegalStateException
	at android.media.MediaCodec.native_dequeueOutputBuffer(Native Method)
	at android.media.MediaCodec.dequeueOutputBuffer(MediaCodec.java:1055)
	at com.genymobile.scrcpy.ScreenEncoder.encode(ScreenEncoder.java:91)
	at com.genymobile.scrcpy.ScreenEncoder.streamScreen(ScreenEncoder.java:72)
	at com.genymobile.scrcpy.Server.scrcpy(Server.java:32)
	at com.genymobile.scrcpy.Server.main(Server.java:133)
	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:256)

 $ adb devices
List of devices attached
<IP_ADDRESS>:5555	device

Restarting adb daemon did any help?

I'm getting an error that there are multiple devices but when I run "adb devices" there is only one listed
This is an error printed by adb on adb reverse over wifi on old devices, but _scrcpy fallbacks to adb forward, so this is not the reason of your error, everything is ok for this part:
https://issuetracker.google.com/issues/37066218
https://www.genymotion.com/blog/open-source-project-scrcpy-now-works-wirelessly/
See #5

java.lang.IllegalStateException
  at android.media.MediaCodec.native_dequeueOutputBuffer(Native Method)

This is the real error. And is the same as #465, so I'm closing as duplicate.


why the experiment can not fully use the memory of GPU

Describe the issue: Hi, I am trying to using NNI to optimize the hyperparameters of a training. When I run the experiment in my Linux server, I found the trials that the experiment run cannot fully use the memory of GPU. Normally if I run the python file, it can use full memory and the training is fast, but  if I run the python file through nni, the training is slow.
please tell me how to fix it. Like the screenshot, the trail by nni only occupy 159MB.

Environment:

NNI version:
Training service (local|remote|pai|aml|etc):
Client OS:
Server OS (for remote mode only):
Python version:
PyTorch/TensorFlow version:
Is conda/virtualenv/venv used?:
Is running in Docker?:

Configuration:

Experiment config (remember to remove secrets!):
Search space:

Log message:

nnimanager.log:
dispatcher.log:
nnictl stdout and stderr:

How to reproduce it?:

Hello, I am also trying to use NNI to optimize the training hyperparameters. When I run NNI on the ubantu server, it always shows "failed". Then, I check the log file and it says "GPU context requested, but no GPUs found.". How can I solve this problem? I look forward to your reply very much, and I would greatly appreciate it.


Content should be a @State variable

The content should be a @State variable, and then we can use it like this.
@State private var json = ""

var body: some View {
	CodeViewer(content: $json)
	.onAppear {
		json = """
		{
			"text": "hello world"
		}
		"""
	}
}

ok, that sounds cool. Feel free to implement it if you have time @L1cardo 👍

ok, that sounds cool. Feel free to implement it if you have time @L1cardo 👍

I really want to implement it, but I need to prepare for my exam.
Can you do that in your spare time?

ok, that sounds cool. Feel free to implement it if you have time @L1cardo 👍

I really want to implement it, but I need to prepare for my exam.
Can you do that in your spare time?

Haha, okay then. Good luck with your exam 💯

version 1.2.0 now supported @State 👍


Add MetaData LLM call

Related to #16
Add an optional LLM call for generating tags and summary of the file.

app/main.py

Add a new endpoint /llm_tags_summary to generate tags and summary using the LLM.
Update the OllamaGenerateRequest class to include a new field generate_tags_summary.
Update the generate_llama function to handle the new generate_tags_summary field.

app/tasks.py

Add a new function generate_tags_summary to generate tags and summary using the LLM.
Update the ocr_task function to include an optional call to generate_tags_summary after extracting text.

client/cli.py

Add a new command llm_tags_summary for generating tags and summary.
Update the main function to handle the new llm_tags_summary command.

.env.example

Add a new environment variable LLM_TAGS_SUMMARY_API_URL.

Thanks this is cool!
I requested minor changes. When applied and when #10 merged I'll also ask you to extend this feature for the metadata to be used within storage strategies to format file names (to use the tags or other fields within file names)

One more thing - please use the defined prompt (can be a env variable with some nice default) to have the prompt used for metadata configurable
It should return JSON object with metadata:
{
 title: "",
 filename_title: "",
 tags: "",
 "summary": ""


Unable to bind server to the specified port: The requested address is not valid in its context

I am using opendnp3 v3.1.1 attempting to connect to a new generation controller installation using TLS.
Starting with the example in master-gprs-tls, I am getting this error with my IPEndpoint and TLSConfig
"Unable to bind server to the specified port: The requested address is not valid in its context."
This my first DNP3 experience and I don't have a lead from that error. Any suggestions\directions on how to investigate if the problem is on my end or the generation controller?

Can you show us what is the IPEndpoint you are trying to bind to?

This was an IP filtering issue.


API calls don't seem to be happening.

Versions:
$ nvm version
v20.11.0
$ npm --version
10.2.4
# let me know what else I can put here.

Running with npm run dev results in a UI, however it doesn't seem to do anything.  Buttons don't work.  Clicking "Add File(s)" interacts with my file manager, but that doesn't seem to upload anywhere on my server.
No API calls are made despite verifying the accessibility.  I see nothing from PrivateGPT logs.  I see nothing in the UI logs, even when running with npm run dev --verbose
I also attempted the same thing by exposing my PrivateGPT instance to the world and using the demo.  No calls reach it, despite being able to remotely curl.
Thanks for reading, let me know what else I can provide.  I'm new to node, so assume the worst. :D

Do you have pgpt running in the background, you also need to enable CORS in PGPT to allow a connection from other urls

I do not have it running backgrounded.  I was going to look at running it with nohup, but for now I have it in a screen session.


Will the code implementation on the SensatUrban dataset be provided?

The same request for additional code on SensatUrban would be appreciated if you could provide, Dr. Hu!
All the best!


fix(deps): update terraform-module

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/cbr/ibm (source)
module
minor
1.28.1 -> 1.29.0

terraform-ibm-modules/cos/ibm (source)
module
minor
8.14.5 -> 8.15.1

terraform-ibm-modules/kms-all-inclusive/ibm (source)
module
patch
4.16.9 -> 4.16.10

Release Notes

terraform-ibm-modules/terraform-ibm-cbr (terraform-ibm-modules/cbr/ibm)
v1.29.0
Compare Source
Features

added cloud logs support to the fscloud submodule profile (#568)

terraform-ibm-modules/terraform-ibm-cos (terraform-ibm-modules/cos/ibm)
v8.15.1
Compare Source
Bug Fixes

deps: update terraform terraform-ibm-modules/cbr/ibm to v1.29.0 (#780) (0496ffb)

v8.15.0
Compare Source
Features

exposed the ability to set the provider_visibility in the DAs Learn more (#779) (cf8787b), closes /registry.terraform.io/providers/IBM-Cloud/IBM/latest/docs#visibility-1

terraform-ibm-modules/terraform-ibm-kms-all-inclusive (terraform-ibm-modules/kms-all-inclusive/ibm)
v4.16.10
Compare Source
Bug Fixes

deps: update terraform terraform-ibm-modules/cbr/ibm to v1.29.0 (#588) (0319e5f)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

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

GitHub release
v1.14.8

Your semantic-release bot :package::rocket:


Recipe Recommender

Scrapes http://whatthefuckshouldimakefordinner.com/ to get a random recipe, providing a preview image and a link to the recipe

This needs a pull from develop

This needs a pull from develop

prob just because of wrong base

This needs a pull from develop

prob just because of wrong base

Well and that this develop branch is out of date

I think the commit history here is messed up, it's giving diffs for things already merged

idk what you just did, it was fine before you did that

Want me to force push a fixed branch?

Please 😔

Still need to use the inherited property, I didn't do that for you. All i did was remove the unnecessary commits and rebase on develop

this is very stale :(


upstream missing instance metadata

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
upstream missing instance metadata
Expected Behavior
upstream carries instance metadata.
Extended label-based load balancing strategy
Steps To Reproduce
No response
Environment
ShenYu version(s):

Debug logs
No response
Anything else?
No response

which version? pls fill the log


Account for physics interpolation and transform snapping when Y-sorting

Makes the transforms used for Y-sorting canvas items match the transforms used for such items in RendererCanvasCull::_cull_canvas_item, aka it accounts for physics interpolation and transform snapping now.
Fixes #92982.

I'll take a look.
I vaguely remember doing something to fix y-sorting at some point but maybe it's not working in 3.x too, I'll check the issue and see if I can reproduce in 3.x.

I can't seem to reproduce so far in 3.x, but then the Y sort works quite differently there. (I'm not super familiar with how 4.x does y sorting.)

IIRC in 3.x the canvas item with sort_y = true is treated as a grouping-only item, it's not drawn itself (the VisualServer implementation seems to be done specifically with YSort node in mind, assuming YSort doesn't draw itself - hence e.g. #49165). I'd guess that's something about that. But yeah, I haven't looked in detail into 3.x in quite a while (we complement each othere here :smile:).

Key things is probably making sure it isn't doing more work than necessary, ideally shouldn't be interpolating transforms twice.

Yes, currently it indeed does interpolate twice per y-sorted item, I'm well aware of that and I do dislike it. Was focusing on conceptually fixing the transform calculations here (in fact I haven't tested it much in action, only in the MRP from #92982; was fixing purely from the code standpoint; so testing further welcomed).
But I think I already know how to avoid this double computation, later today I will probably push a second commit in here (such change seems more regression prone so I think leaving it as a separate commit would make sense).

@kleonc Oof! I never even imagined anyone would use a parallax effect with y-sorting... and I still can't think of a use case, but I'm sure someone can and will be very upset! I tried it on the master branch and it seems to remove all repeats, but everything else seems to be working so I guess that's the only thing we'll need to suss out.

@markdibarry Firstly let's clarify of what behavior of y-sorting + repeating we're talking.

y-sortedno repeat
(1) repeats y-sorted separately
(2) repeats y-sorted as one item together with the original one

Knowing a little how these work I intuitively was thinking about (2) but I guess someone could expect (1).
(1) seems not feasible performance-wise to me, as it would require each repeat to basically become its own item to be ordered separately (thus in case of items' different materials more batching breaking etc.; way costlier/slower).
(2) should be easy to achieve. Actually it already works in some cases. :upside_down_face:
Also given it's questionable whether it has a use case I'd

I tried it on the master branch and it seems to remove all repeats due to _cull_canvas_item() using a completely different culling approach when y-sorting and (from the look of it) removing all parent/child relationships...

I've looked into the repeating code and main issue is that for all y-sorted items _cull_canvas_item() is called with repeat_size and repeat_times of the y-sorted subtree's root item. While y-sorted repeat source items (repeat_source == true) will override these for themselves, their original children won't get such values. And that's pretty much all what's preventing (2) from just working.
Meaning it already works e.g. if Parallax2D is the first y-sorted node (the root of the y-sorted subtree) and there are no nested Parallax2Ds involved etc.
In v4.3.beta1.official [a4f2ea91a]:

Fixing it would be pretty much the same as what's done in this PR, aka it's a matter of propagating proper repeat_size and repeat_times when preparing y-sorting, and skip the current code determining these in case we're dealing with an already y-sorted item.
There are some other little issues with the repeating I can see in code, but it's offtopic here.
In general I dislike how now things need to be duplicated codewise to be done before y-sorting, so I'm thinking _cull_canvas_item should likely be splitted / refactored a little, but this I consider as for after 4.3. But again, out of scope of this PR, it was meant to be asimple fix. :upside_down_face:

@kleonc Thanks for the advice! Made an issue and PR here: #93182

Rebased (#93182 was merged).

Needs a rebase, and then an approval would be great :)

Rebased (pretty much no changes compared to the pre-rebase version).

Besides the above comment the code looks fine to me.

Am happy that @rburing has checked properly, I've had a little look through and it looked fine but I didn't follow it completely. :grin:

Thanks!

Hmm, this change replaces the floor + 0.5 math with round, basically undoing #93740. Was this intended?

Hmm, this change replaces the floor + 0.5 math with round, basically undoing #93740. Was this intended?

Absolutely not. It was like that originally and I must have overlooked this while rebasing, my bad. Thanks for spotting it out!

Note: if/when cherry-picking, should be done together with #98195.


Develop

Merge develop to master

Coverage increased (+8.7%) to 81.974% when pulling 48992a1c2985123166fdd24912a63eea2cf43706 on develop into aee0f5b13e0a196123a1a36da544381878a427b9 on master.


Use more elf::shf constants

I'm curious if https://github.com/davidlattimore/wild/blob/fe307369b9b815ea5226fe1c2eac7b2e0f9beedd/linker-diff/src/header_diff.rs#L93-L123 can also be moved to wild_lib::elf::shf module to a helper function?
If so, should I then add a dependency of wild_lib for linker-diff? Or should I move it to linker-util?

If so, should I then add a dependency of wild_lib for linker-diff? Or should I move it to linker-util?

Either is fine with me. At one point wild_lib had an optional dependency on linker-diff, which would have prevented the reverse dependency, but I removed that in favour of just executing linker-diff, since actually depending on it inflated the binary size too much.
Actually, thinking about it some more, for it to be used from linker-diff, it'd need to be pub. If you're looking through the API docs for the linker, then a function like that might be surprising, since it's probably not an API that a user of the linker would even need. So maybe linker-util makes more sense.

So maybe linker-util makes more sense.

Good, I've just made #78 that addresses that.


Finish GameWorldAnchor

GameWorldAnchor has critical unimplemented features. GameRegions cannot be used correctly until this is corrected.

GameWorldAnchor is no longer used


Adds explicit binding of flexible price request forms to courseware objects

Pre-Flight checklist

[X] Migrations

[X] Migration is backwards-compatible with current production code

[X] Testing

[X] Code is tested
[X] Changes have been manually tested

What are the relevant tickets?
#724
What's this PR do?
Adds a couple of fields and relations to the FlexiblePriceForm to link them directly to a Course or Program object. Also updates the submit logic to retrieve the correct courseware object based on some rules.
The courseware object can be retrieved through the get_parent_courseware function (was get_parent_product), which returns one of (in order):

The selected program, if there is one
The selected course, if there is one
The parent page's course, if there is one

Prior to this, the model would only look at the form's place in the page hierarchy to determine the courseware object. This allows us to set up a Flexible Pricing request form for a program without having to have program pages in the system. When the system games program pages, the logic here should be updated to pull the parent page's program as well.
How should this be manually tested?
All automated tests should pass.

Create or edit a flexible pricing request form.
You should see dropdowns for Course and Program. Set one or the other. (If you set both, the Program takes precedence.)
Save the form, and submit a request through the form.
The resulting submission should be linked with the appropriate courseware object.

Codecov Report

Merging #787 (b0e1927) into main (ced425c) will increase coverage by 0.00%.
The diff coverage is 71.42%.

@@           Coverage Diff           @@
##             main     #787   +/-   ##
=======================================
  Coverage   85.52%   85.53%
=======================================
  Files         129      129
  Lines        5735     5743    +8
  Branches      942      945    +3
=======================================
+ Hits         4905     4912    +7
- Misses        680      681    +1
  Partials      150      150

Impacted Files
Coverage Δ

cms/models.py
71.25% <71.42%> (+0.12%)
:arrow_up:

ecommerce/discounts.py
80.70% <0.00%> (+1.75%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


#8 - Implement type jailing for every public method calls

Provides implementation for #8
What happens:

method is called
parameters are iterated
parameters that are type-hinted with an interface are replaced with a type-jail
type-jail ensures that any call on the object MUST be within the boundaries of the interface

Note: the fatal looks like a GO-AOP-PHP failure, but it is in an expected failure case anyway, so... Not an issue :P


OpenAI Chat Completion request stream property should be true/false, not True/False

What happened?
OpenAI Chat Completion stream property is a boolean true/false, yet Autogen sets the value to True or False. Here's a sample intercepted JSON payload:
{
'messages': [
{
'content': 'You are a helpful AI assistant. Solve tasks using your tools. Reply with TERMINATE when the task has been completed.',
'role': 'system'
},
{
'content': 'What is the weather in New York?',
'role': 'user',
'name': 'user'
},
{
'tool_calls': [
{
'id': 'call_iZKkdwu577dckxO14WkcFvJS',
'function': {
'arguments': '{"city":"New York"}',
'name': 'get_weather'
},
'type': 'function'
}
],
'role': 'assistant',
'name': 'weather_agent'
},
{
'content': 'The weather in New York is 73 degrees and Sunny.',
'role': 'tool',
'tool_call_id': 'call_iZKkdwu577dckxO14WkcFvJS'
}
],
'model': 'gpt-4o-2024-08-06',
'stream': False,
'tools': [
{
'type': 'function',
'function': {
'name': 'get_weather',
'description': '',
'parameters': {
'type': 'object',
'properties': {
'city': {
'description': 'city',
'title': 'City',
'type': 'string'
}
},
'required': [
'city'
]
}
}
}
]
}
Note: stream property value is False, not false, which is incorrect according to JSON schema
What did you expect to happen?
Expect the steam value to be set to true or false
How can we reproduce it (as minimally and precisely as possible)?
Take weather agent sample and log outbound requests to OpenAI LLM
AutoGen version
0.4.0.dev8
Which package was this bug in
Core
Model used
No response
Python version
3.12
Operating system
No response
Any additional info you think would be helpful for fixing this bug
No response

@qcloop thanks for the issue. Are you interested in fixing this by submitting a PR?
you can take a look at the developer guide in python/README.md.