text:
Minor Bug - Incompatibility with module Token Faction

Environment Details
Foundry VTT Version: 0.8.9
Operating System: [Linux]
How Are You Using Foundry: [Linux,Native Application (Electron), Chrome]
Which Game System: Dungeons and Dragons 5th Edition, version 1.4.2
Modules Enabled?: Yes (if you need i can give you the full list)
Module version: 2.8.11
OS, Hosting, Browser (if applicable): Linux/Node/Chrome
Description of the issue:
Hi I was updating the Token Faction module (integrating a little better the wrapper library and other minor bug fixes). With the perfect-vision module I get an error which I highlight below.

The error appears to originate from something in the "patch" method
How do you prefer to manage it? I can also safely edit the code on my side if you have any suggestions.

Hi! I need to be able to hook the function that creates/adds the factionBase, i.e., updateTokenBase. Or I can patch Token.prototype.addChild, but then I need factionBase to have a unique name so that I can recognize it. See here: https://github.com/dev7355608/perfect-vision/blob/main/scripts/modules/token-factions/index.js. And I would be nice, if factionBase wasn't destroyed every time, but created/added once and cleared instead.

Hey @dev7355608  after writing a (hopefully working) new version of the Token Faction method, in theory it should be enough to hook the "TokenFactions.updateTokenFaction" method , but tell me if I can do more.
With no patch on Perfect vision module , there is no exception, just a strange behaviour with the zIndex on the token
Without perfect vision active:

With perfect vision active:

P.S. I removed the "destroy" method on Pixi container in favor of the "clear" method

@dev7355608  so an even better solution for you would be to use a customization "Token.prototype.drawFactions" function as for the "Token Aura" module here?

@p4535992 I just saw that you registered PV as a minor conflict. Could you remind me what the issue is exactly?

I can no longer replicate the error I had at the time, I remember that it was an exception on the logs that I could ignore, but now it does not appear anymore I guess it has been resolved, I update the 'changelog' accordingly.


text:
Add vscode-cli

Fixes #565

Thanks for the contribution!
It appears the tests are failing because of line 21 in install.sh file (an extra ; char)
Ill be happy to merge once you fix it - or alternatively you can give me push permissions to the branch and ill handle the minor fixes and merge it

Whoops! I took care of it. Thanks!

source: gharchive/pull-request

repo: devcontainers-contrib/features

license: MIT

license_type: permissive

license_source: github-api


text:
@joshspicer [https://apps.apple.com/tw/app/星城online-星幣爭霸戰搶億%

          @joshspicer [https://apps.apple.com/tw/app/%E6%98%9F%E5%9F%8Eonline-%E6%98%9F%E5%B9%A3%E7%88%AD%E9%9C%B8%E6%88%B0%E6%90%B6%E5%84%84%E8%90%AC%E5%BD%A9%E9%87%91/id919043762](htt`https://www.bing.com/fd/ls/GLinkPing.aspx?IG=60B0D2239CD5446EA09B81C274DBF66A&&ID=SERP,5177.1&SUIH=4ieSXRL9zCbYVzCgp9nqpA&redir=aHR0cHM6Ly9hcHBzLmFwcGxlLmN`)

Originally posted by @Gesisfm in https://github.com/devcontainers/spec/issues/196#issuecomment-1418263045

Hi there, it seems this may have been opened by mistake. If you have a feature request or bug related to this repo, please let us know. Thanks!

#143
https://www.bing.com/fd/ls/GLinkPing.aspx? IG=60B0D2239CD5446EA09B81C274DBF66A&&ID=SERP,5177.1&SUIH=4ieSXRL9zCbYVzCgp9nqpA&redir=aHR0cHM6Ly9hcHBzLmFwcGxlLmNvb@Gesisf

source: gharchive/issue

authors: Gesisfm bamurtaugh

repo: devcontainers/action


text:
mcr.microsoft.com/devcontainers/base:ubuntu is still focal?

The README says it is the latest LTS version, but it doesn't seem to be the case.
https://github.com/devcontainers/images/blob/35c84eded76ba0fb5ac6635c066022ab381e755e/src/base-ubuntu/README.md?plain=1#L24
Note that docker.io/library/ubuntu:latest has already switched to jammy right after jammy was released half a year ago.

Thanks @eitsupi!
@samruddhikhandale I see this too - should we switch to Jammy, or update the readme?

Created PR - https://github.com/devcontainers/images/pull/179 which switches to jammy.
Thanks @eitsupi for catching this! ✨

Released dev tags which switches base:dev-ubuntu to jammy, looks good. I will release prod tags now.

// cc @Chuxel

https://github.com/devcontainers/images/pull/179 is live now which uses jammy 🚀

authors: bamurtaugh eitsupi samruddhikhandale

repo: devcontainers/images


text:
Using container element the right way

VirutalList attempts to directly add the needed event listeners directly to the DOM element. I have found this can cause the error Cannot read property addEventListener of null in certain cases, because componentDidMount on the virtual list is being called before the parent has rendered.
Is there any obvious work-around for this or is there something wrong with our lifecycle management?

Hmm, nothing obvious comes to mind.  Would you be able to post the relevant code, and also your exact version of React?  I'd love to take a closer look.

@CAYdenberg Do you happen to have any more info around this?

We've worked around and aren't using refs. I will close this for now and let you know if I come across it again.

Thanks @CAYdenberg - I'm going to come up with another demo implementation just to be sure things are working properly.

Hey @CAYdenberg - may I ask how did you solve this issue?
@developerdizzle - will you have time to add another demo with a default container (on load)?

Like we aren't using refs currently. IIRC, we needed it to set the scrollbar, but we worked around by just using window scroll and reworking some other element positioning.
If I circle back to this at some point I'll be sure to update this.

+1 to this issue, even it's closed

I spent a lot of time to get this working correctly but I couldn't unfortunately
the only thing I could think of (couldn't get it to work though) is to use a closure to only initialize the list once and call it from the render method (after the refs has been updated)
and everytime you call the this method again it will return a reference to the initalized list

I slept on it and found a solution,
I initialized the list in ComponentDidMount where you have access to the refs
And saved the list in the state
  componentDidMount() {
    this.setState({
      VList: VirtualList({
        container: this.refs.usersContainerRef,
      })(this.listOptions),
    });
  }

and in the render method I used the initialized component:
<this.state.VList items={} itemHeight={} />
and it worked!

authors: CAYdenberg Shaked developerdizzle muhammad-saleh studentIvan

repo: developerdizzle/react-virtual-list

license: mit

license_source: bigquery


text:
Fix crash if config doesn't have an email section

The "email" section of config.json is marked in the documentation as optional, however jekyll-hook crashes if it can't find this section.
This change fixes that bug by checking if the section exists before accessing the email.isActivated value, rather than afterwards.

:+1:

authors: cmrn parkr

repo: developmentseed/jekyll-hook


text:
options: added delete & delete-all

**solved issue #50 **

Added both individual delete and delete-all option

Demo

@underscoreanuj This works fine, but the UI looks pretty messed up I think maybe you should use a x icon instead of explicitly creating a delete button. And please take care of the alignment as well.

3 dot hover dropdown to each card which can later be extended to add more options.
0% scroll representation (sometimes the % div would not show up due :

let percentage = Math.round((urls[url].offset / urls[url].total) * 100);
yielding a value of zero.
).

"Fetching Saved Scrolls..." / "Empty!!!" / "All Saved Scrolls" automatic switching.

@underscoreanuj Can you move the three dot menu inside the card.

@underscoreanuj I have made some minor style changes and opening the menu on onclick instead of hover. Can you please test it from your end as well once and let me know if anything is wrong?

@all-contributors please add underscoreanuj for code

@underscoreanuj I have made some minor style changes and opening the menu on onclick instead of hover. Can you please pull it and test it from your end as well once and let me know if anything is wrong?

looks great to me.

repo: devfolioco/scrroll-in


text:
PDFKIT Install Procedure > Request

I've spent 4 days exploring PDFKIT/NODE as a solution for lambda based PDF generation....  and I've yet to get PASSED the install successfully more than once.
AWS EC2 + AMZ Linux Flavor
STEPS USED
EC2 Create AMZ LINUX
As EC2-user
COMMANDS
cd /home/ec2-user/
curl https://raw.githubusercontent.com/creationix/nvm/v0.23.3/install.sh | bash
source ~/.bashrc
nvm install stable
nvm use v7.10.0
cd /var/www/html/
npm install pdfkit
node t.js   <here NODE is executing a test of PDFKIT)
Sometimes PDFKIT installs without errors.. sometimes I get complaints it seems.
Goal is to explore PDFKIT for viability, but I need to form a reliable environment, and that's not yet been what I'd call ideal.
PLEASE SUPPLY AN IDEAL SETUP PROCEDURE from start to finish so I can explore PDFKIT for viability.
If another path is suggested due to maturity, I invite that direction
n8

What errors are you getting?

I usually get the following... but then once I get PDFKIT installed, I can't find viable test syntax... everything errors out due to syntax..  Syntax reference available?
npm WARN enoent ENOENT: no such file or directory, open '/var/www/html/package.json'
npm WARN html No description
npm WARN html No repository field.
npm WARN html No README data
npm WARN html No license field.
It appears I can get to SOME form of functional readiness... which I think I have at now.
Based on latest NODE 7.10... I'm testing PDFKIT for viability, and things as simple as TEXT adding.. errors all over from the examples...

I have had mixed results installing.. likely due to my inexperience w NODE and when/where to use which user type
i've achieved enough at this point to get what I needed, so this can close, however an UPDATED FINAL/CLEAN install document would be great for elimination of time waste, and incorporation for someone like myself exploring w little time.
thanks! :)

See #670. The plan is to convert from coffeescript to JS soon.

authors: ctoxyz devongovett

repo: devongovett/pdfkit


text:
[style]: Improve UI of the What our Member says about us section.

What's the style idea?
I would like to improve the ui of  What our Member says about us section to make it more attractive by adding some cool effects and also by adjusting the existing css.
So,please assign this issue to me under gssoc'23.
Add screenshots

Code of Conduct

[X] I agree to follow this project's Code of Conduct

How do you plan on improving the UI?

How do you plan on improving the UI?

I would like  to add some hover effects and box-shadows also would like to adjust the css like margin, padding, etc.

repo: devs-in-tech/DevsInTech


text:
[dexie-cloud] http 449 eror on sync

Looking at the docs here on the project manager code I implemented something similar.  However, i was getting a HTTP 449 on sync after executing something like this
const realmId = await db.realms.add({
  name: `Team ${name}`,
  represents: "A baseball team",
});

const id = await db.teams.add({
  name,
  realmId,
  organization,
  playerIds: [],
  gameIds: [],
});

I needed to update the code to the following for it to work:
  const realmId = await db.realms.add({
    name: `Team ${name}`,
    represents: "A baseball team",
  });

  await db.members.add({
    realmId,
    roles: ["manager"],
  });

  const id = await db.teams.add({
    name,
    realmId,
    organization,
    playerIds: [],
    gameIds: [],
  });

Although that resolves the issue im a bit confused here.

I'm not specifying an email or userId in db.members.add, just the realmId that was just created with the "manager" role, is it using the the userId that is currently logged in by default? I assume when trying to share I need to add the other userId (which is the email i think). My roles and schema are below.
If a user creates a team object without logging in, then logs in, i was expecting the team object to persist. However the previously created team data is gone (as well as members) after logging and sync occurs and the unauthorized user is not merged with the logged in user.  Is it possible to do that?
Trying to understand db.members.add:

await db.members.add({
  realmId,
});

^^^ creates a single member object like this:

Its an edge between the user and realm, right?
However creating a member like this creates two member rows in the member table:

await db.members.add({
  realmId,
  roles: ["manager"],
});

I assume thats an edge between the role and and realm, right?  I' am trying to assign the current user a "manager" role to this object, but it seems it really is not needed because the current user is the owner and the only edge that matters is the first one. Is that correct?

Each member must have at least a realmId and an email property

I'm not passing an email property at all, but it seems to be working and using my email as the userId. Is email necessary when I'm just assigning permissions to the current user?
Schema details
{
  "roles": {
    "manager": {
      "displayName": "Manager",
      "description": "Members with this role gains full permissions within the realm pointed out by the member entry",
      "sortOrder": 1,
      "permissions": { "manage": "*" }
    },
    "coach": {
      "displayName": "Can edit data but cant manage",
      "description": "Members with this role can create friends within a realm and update whether a friend is a good or not",
      "sortOrder": 2,
      "permissions": {
        "add": "*",
        "update": "*"
      }
    },
    "readonly": {
      "displayName": "ReadOnly",
      "description": "Members with this role have no permissions to change any data",
      "sortOrder": 3,
      "permissions": {}
    }
  }
}

export class GamePlanner extends Dexie {
  teams!: DexieCloudTable<ITeam, "id">;
  players!: DexieCloudTable<IPlayer, "id">;
  games!: DexieCloudTable<IGame, "id">;
  innings!: DexieCloudTable<IInning, "id">;

  constructor() {
    super("GamePlanner", {
      addons: [dexieCloud],
      cache: "immutable",
    });
    this.version(1).stores({
      teams: "@id, name, organization, *playerIds, *gameIds",
      players: "@id, firstName, lastName, number, *teamIds",
      games: "@id, date, *inningIds, *playingIds, *notPlayingIds, updatedAt",
      innings: "@id, *dugoutPlayerIds, *fieldPlayerIds, gameId",

      // access control
      realms: "@realmId",
      members: "@id",
      roles: "[realmId+name]",
    });

    this.cloud.configure({
      databaseUrl: process.env.NEXT_PUBLIC_DEXIE_CLOUD_URL!,
      tryUseServiceWorker: true, // true!
      requireAuth: false,
    });
  }
}

Thanks! Looking in to this...

Issue confirmed. It happens when creating a realm without members. Issue solved in staging (version 1.2.8).
I've lifted your (@j-5-s) databases to staging so you should be able to verify it now. Let me know if you create a new db and need it to have the fix.
I'll wait some days before lifting production to latest version and switching staging db's back to prod, but probably within a few days. If there's someone else in need for this fix asap, please let me know.

thanks @dfahlander. No rush on my end. So that i understand whats happening though, the 449 error shouldn't happen when just creating a new realm and assigning it to another object?

Exactly, that's totally correct. In a previous version the flow required was to also explicitly add a member that connected your own userId to the new realm. This requirement was taken away and instead managed automatically on the server - it creates the "self member" automatically for the user that created the realm so there's no need to do so, but the issue was a consistency check later in the flow that compared the original request with the actual mutations and detected this inconsistency and threw the 449 error. So it's perfectly ok to create new realms without creating members.

thanks! I think I understand: Is it correct to think about the user who creates a realm as a the "owner" member which gives manager level privileges and not necessary to add any permissions or roles to that member.  That said,

If a member is removed from a realm, objects connected to that realm that are owned by the user will go out of scope for the use

I seem to have 5 or 6 realms that i have removed my user from and no longer have access to those scopes.  Is there a way on the cli or other interface to cleanup data?

Correct. You have full access on the entire DB only when using the CLI or the the REST API's POST /all/members. Use dexie-cloud export to export an individual realm. Example:
dexie-cloud export --data --realmId "rlm~tdl0Ofo426bilS6y3fWMn6BNqA|zed" exportfile.json

Use a text editor to change the properties of one of the existing members or add a new one (ID must start with 'rlm' but could be of any length and chars). Use dexie-cloud import to import it back.
dexie-cloud import exportfile.json

If you prefer using the REST api, you can create new objects and let the server can generate their primary keys (on '@' based tables):
Create new member
POST /all/members HTTP/1.1
Authorization: Bearer xxxxxx
Content-Type: application/json

[{
  "realmId": <theRealmId>,
  "userId": <yourUserId>,
  "roles": ["manager"]
}]

Update existing
POST /all/members HTTP/1.1
Authorization: Bearer xxxxxx
Content-Type: application/json

[{
  "id": <memberId>,
  "realmId": <theRealmId>,
  "userId": <yourUserId>,
  "roles": ["manager"]
}]

FYI: Production is now on version 1.2.8 also so the fix has reached all customers and your dbs is back in the production slot.


text:
Async changes in updating hook

I am trying to figure out the best approach for using hooks to add some fields to an object when it gets stored or changed.
The basic idea is there are entry objects which must contain a bunch of properties that are based on some complex queries and calculations of other entries. These calculated properties are all stored under a property called derived. It would far prohibitively expensive to calculate entry.derived every time it is needed, or when it is read from the DB. Instead I opted to populate the derived property ahead of time, and hooks seem to be the best place to do this.
This seems to be no problem for the creating hook. However, I also need to re-generate derived if any other property in entry is changed. The updating hook requires I submit additional changes by returning them, which is problematic because the only way I can generate the change is via an async call.
Below is some minimal code that tries to demonstrate the problem. I haven't tried option B yet, but I suspect it won't work either.
const entryDerivedData = function(entry) {
    // query a bunch of data from entries table then do some calculations
    return db.entries.where('exerciseID').equals(entry.exerciseID).toArray()
        .then(e => {
            // do some calculation and return
            return calculateDerivedData(e);
        });
};

// A: Can't do this because `hook` isn't expecting a generator func
db.entries.hook('updating', function*(mods, primKey, entry, transaction) {
    const derived = yield entryDerivedData(entry);
    return derived;
});

// B: Another possibility, but probably won't work either
db.entries.hook('updating', function(mods, primKey, entry, transaction) {
    transaction.scopeFunc = function() {
        return entryDerivedData(entry)
            .then(derived => {
                // Won't this result in another invocation of the updating hook?
                return db.entries.update(entry.id, {derived});
            });
    };
});

Unfortunately, hooks are synchronous and there's no way to do async calls within them. This is something that is going to change but I cannot promise when. Hoping to rewrite the hook framework within the next 6 months or so and allow bulk hooks (more performant) that can be async (keeping backward compatibility for existing hooks).
Until then, you could utilize the fact that the hook is always called within a transaction (no matter whether the user does an explicit transaction or not), and you can do additional operations onto the current transaction. Just need to make sure you don't end up in an infinite loop as your additional changes may trigger your hook again.
An example would be this:
db.entries.hook('creating', (primKey, entry, trans) => {
  entryDerivedData(entry).then(derived => {
        db.entries.update(primKey, { derived }).catch (e => {
            // Failed to update. Abort transaction or rethrow error:
           throw new Error ("Could not make sure derived property was set properly");
        });
    });
});

db.entries.hook('updating', (mods, primKey, entry, trans) => {
    if ('derived' in mods) return; // We're the one triggering this change. Ignore.
    // First, apply the mods onto entry:
    var entryClone = Dexie.deepClone(entry);
    Object.keys(mods).forEach(keyPath => {
        if (mods[keyPath] === undefined)
            Dexie.delByKeyPath(entryClone, keyPath);
        else
            Dexie.setByKeyPath(entryClone, keyPath, mods[keyPath]);
    });

    entryDerivedData(entryClone).then(derived => {
        db.entries.update(primKey, { derived }).catch (e => {
            // Failed to update. Abort transaction or rethrow error:
           throw new Error ("Could not make sure derived property was set properly");
        });
    });
});

If you really need to enforce that the user cannot change "derived" property without enforcing your policy, you would need to assure that the hook caller is yourself. This is possible to accomplish via zones / Dexie.PSD:

const secretProp = Math.random().toString();

db.entries.hook('updating', (mods, primKey, entry, trans) => {
    if (Dexie.Promise.PSD[secretProp]) return; // We're the one triggering this change. Ignore.

    ...

    Dexie.Promise.newPSD(()=>{
        // You enter a new zone that will be derived for all async calls
        // originating from this scope. Mark the zone with a private property:
        Dexie.Promise.PSD[secretProp] = true;

        entryDerivedData(entryClone).then(derived => {
            db.entries.update(primKey, { derived }).catch (e => {
               // Failed to update. Abort transaction...
               throw new Error ("Could not make sure derived property was set properly");
            });
        });
    });
});

Thank you! I did not think of checking for derived in the mods object, now that you've shown me it looks like an obvious solution (until async hooks are ready).
By the way, why is this necessary?
// First, apply the mods onto entry:
var entryClone = Dexie.deepClone(entry);
Object.keys(mods).forEach(keyPath => {
    if (mods[keyPath] === undefined)
        Dexie.delByKeyPath(entryClone, keyPath);
    else
        Dexie.setByKeyPath(entryClone, keyPath, mods[keyPath]);
});

Isn't this going to happen already anyway after the hook returns?

Yes it's going to happen anyway, but in case your code (entryDerivedData) depends on the updated property, like excerciseId, or would expect an object where the mods has been applied

Sorry, one more follow-up to this..
How are hooks and schema upgrades meant to work together? What's happening is that I implemented the hooks as described above (thanks again!), however, the hooks are of course written with the current schema in mind, but it appears that the upgrade function is called before the schema is fully migrated.
Basically, the entryDerivedData function depends on a new store/table that was added as part of schema version 2 and it's getting called in the hook when the migration is taking place.
db.version(0.2)
	.stores({ entries: ..., exercises: ... })
	.upgrade(transaction => {
		return transaction.entries.orderBy('start').modify(function(entry) {
			// Replace old entry with slightly different one (`derived` object is wiped out)
			// This results in a call to one of the hooks which tries to use the `exercises` table that doesn't exist yet.
			this.value = {
				id: entry.id,
				...
			};
		})
		.catch(function(err) {
			throw new Error(`Failed to migrate schema. ${err}`);
		});
	});
db.version(0.1).stores({entries: '++id,start,xid'});

I suppose I could use Dexie.PSD to prevent the hook from getting called, then somehow manually trigger the re-generation of derived on every entry after the migration is done. Is there a better way?

Hooks are not meant to run during upgrades. If they do, it's a bug. If a developer changes or adds hooks between versions, it's up to the developer to add an upgrader that transforms the data to the new format. That's how it "should" work, but...
The upgrade framework is in need of a rewrite (#105, #287) that was initiated in pull request #293 but have gone stall. It's my plan to go through it and make sure it works as indended. Especially, issues like the one you recently got, happens when the "installed" db is not in sync with the declared db, which can happen of many reasons.
Any inputs of how you would like it to work, are welcome, so I could take those into consideration when rewriting it.

Especially, issues like the one you recently got, happens when the "installed" db is not in sync with the declared db, which can happen of many reasons.

This might be what happened for me. I recall getting some exceptions during an upgrade while developing, and instead of starting from a clean environment I kept working from there. I haven't tried to reproduce this yet but I suspect the hook will not fire (as expected) once I do this cleanly.

it's up to the developer to add an upgrader that transforms the data to the new format. That's how it "should" work, but...

This is tricky for me.. because I am adding a new table which will be used in the hook once the upgrade is complete. To make things more complicated, the new table is populated from JSON (using the method described here) so I can't use the underlying data during the upgrade function because it can't be async.
Is there a hook for when a schema upgrade has completed? The only solution I can see is possibly having some kind of fillDerivedFields() function that gets called after each schema upgrade. This ensures all tables required for filling derived fields exist and hooks are available. I don't see this capability documented anywhere though.

Update on some topics brought up this issue: the error I was getting while migrating was actually due to #473. It's also worth noting that I think my initial issue was approaching the problem incorrectly in the first place. Having the entry derived data on the entry itself made things more complicated in the hook because it required some mechanism to prevent the hook from triggering itself (see Dexie.PSD and other suggestion from @dfahlander above).
The ultimate solution was to normalize the data. Have the derived data of the entry live in its own table means that hooks on the entries tables can write to the deriveddata table and not worry about triggering itself.
Additionally, using Dexie.Observable instead of hooks means I don't have to manually apply the mods in the updating hook since the observable happens after the data is committed.
With this, I am no longer in need of async hook, but they are likely still useful to have.

authors: cfilipov dfahlander


text:
Add freeze command

Similar to pip freeze, create a command that takes all current  (on disk) versions and adds revisions/branches or tags for each project.

What kind of output would you expect from this command? Git and SVN?
Something like:
Scenario: Git projects are specified in the manifest
    Given the manifest 'dfetch.yaml'
        """
        manifest:
          version: '0.0'

          remotes:
            - name: github-com-dfetch-org
              url-base: https://github.com/dfetch-org/test-repo

          projects:
            - name: ext/test-repo-rev-only
              revision: e1fda19a57b873eb8e6ae37780594cbb77b70f1a
              dst: ext/test-repo-rev-only

            - name: ext/test-rev-and-branch
              revision: 8df389d0524863b85f484f15a91c5f2c40aefda1
              branch: main
              dst: ext/test-rev-and-branch

        """
    When I run "dfetch freeze"
    Then the output shows
        """
        Dfetch (0.1.0)
          ext/test-repo-rev-only==master@e1fda19a57b873eb8e6ae37780594cbb77b70f1a
          ext/test-rev-and-branch==main@8df389d0524863b85f484f15a91c5f2c40aefda1
        """

The goal is to: if a user didn't use a revision or branch in his manifest, he can add these automatically with dfetch freeze. The output should be somewhat similar to the check command and strive to keep it the same for git and svn. If I remember correctly the Version class has a __repr__ method. You can then print the version using that. "Freezing version {version}".
Implementation wise, all data should be in the dfetch_data.yaml metadata file. If it's a tag, only mention the tag, if it is a branch, use branch and commit. This should already work as mentioned above through the Version class. The hard part is changing the manifest.
Sidenote: Also consider the case that the current directory contents has a different hash than in the dfetch_data.yaml metadata file. (But this probably should be a different issue/feature).

I've created a branch feature/freeze-command for this.

authors: ben-edna jgeudens

repo: dfetch-org/dfetch


text:
Improvement suggestions

Hi, I would like to suggest some improvments.

The TransactionReceipt and ApprovalReceipt structures are not standardized. This means clients cannot uniformly be notified, if an ERC-20 transaction or ERC-20 approval happened.

The method signatures for some of the methods are incorrect. For example  transfer and approve methods return only a bool, so there is no way for a client to know the transaction id or approval id. In fact transfer should return a TransactionReceipt while approve should return an ApprovalReceipt.

There are methods like burn or mint that really shouldn't be in a standard, as for most tokens they are meaningless. Most ERC-20  tokens have a constant supply of tokens and cannot meaningfully implement a method like that. Those methods could be part of an other standard on top of ERC-20.

We should be more specific about the schemantics of the approve method. For example, let's say I have a token balance 100 tokens. In this case, if I want, then it is allowed for me to approve withdrawals greater than my balance let's say 150.

Rust code needs improvments for example your mint method allows anyone to mint money. Token supply and other data should be in the stable memory and not initialized every time imho.

Thanks for the feedback.
About 1 & 2, we are going to add better error handling than just booleans.
About 3, we try to provide a complete token template for developers, so we included the mint & burn functions in the current implementations, devs can choose to keep them or not when they use it to deploy their own tokens.
About 4, are you saying we should limit the max amount a user can approve according to his/her balance? So if I have 100 tokens, then the max amount I can approve is 1.5 * balance which is 150? This will prevent the unlimited approval problem on Ethereum, more secure, but less user-friendly, because I may have to approve again when the allowance is not enough.
About 5, fixing it now.

thank you, regarding point 4 I am suggesting to do the same as Etherum and allow unlimited approval. We should just mention this in the token standard that it is allowed, so every token will implement it the same way.
Regarding point 3, maybe we could just mention that that those points are not part of the (narrower) ERC-20 standard, but they can be implemented on top of that. So people would now what it means to have an ERC-20 compatible standard (don't have to second guess about those 4 methods)

Agreed

5. Rust code needs improvments for example your mint method allows anyone to mint money. Token supply and other data should be in the stable memory and not initialized every time imho.

it fixed in https://github.com/dfinance-tech/ic-token/blob/2dd08eaf60/rust/src/main.rs

discussed this issue and many more, this ticket became very outdated, so closing it

authors: ccyanxyz ferencdg flyq

repo: dfinance-tech/ic-token


text:
Docs for TrieMap module

I followed @kritzcreek's example in HashMap.
One question for the hyperlinks: What happens when we produce non-html output?
The current links seem brittle and likely to break, right? (or link to the wrong kind of document when we generate non-html output?)

One question for the hyperlinks: What happens when we produce non-html output?

They just appear unescaped as the text in the comment. Not pretty but can at least be deciphered.

The current links seem brittle and likely to break, right?

They are. We'll need to come up with a referencing schema. My plan is to start with the intra-rustdoc RFC and see how far that would get us. I fear it'll involve me writing/extending an OCaml Markdown parser which I'm not excited about.

Looks like @kritzcreek needs to approve again

Looks like @kritzcreek needs to approve again

What's the reviewer semantics here?  I'm afraid that (as usual), I may be misunderstanding some aspect of GitHub : )
For instance, is it preferable to have more reviewers for a quick review, or fewer (e.g., do they all need to re-approve  every commit)?

authors: crusso kritzcreek matthewhammer

repo: dfinity/motoko-base


text:
Article 2104.05240: v2 exists, but generated HTML is from v1

Exact location of issue
The problem is in https://ar5iv.labs.arxiv.org/html/2104.05240#bib . The References section contains a correction of a citation that was made between v1 and v2 and is not reflected in the ar5iv copy.
Problem details
Article https://ar5iv.labs.arxiv.org/html/2104.05240 is generated from https://arxiv.org/abs/2104.05240 . The arXiv URL points to v2, because the authors of the article cited me incorrectly in v1.
Changing the "x" to a "5" produces an HTML5 version of v1 of the article, which contains this incorrect citation. I cannot find an HTML5 version of v2.
(Optional) Expected behavior
ar5iv pages should be made from the latest arXiV version of a paper, not the earliest.
Desktop (please complete the following information)

OS: Windows
Browser: Firefox

(Optional) Additional context
This is a problem that I and others discussed with Deyan Ginev when he deployed the prototype of ar5iv. He acknowledged the problem and was concerned about it, but at the time he said that he had no ability to fix the problem because he didn't have access to all of arXiV's versions, only a data export that contained the v1 of each article.
He indicated that if ar5iv were to become an official arXiv project, it would have access to the correct data and be able to render the latest version of each article.

Cross-referencing the general "enable lastest versions" issue #48  here, thank you for letting me know!
We are now on a path to updating our sources to the latest available ones in arXiv, but it may take a little time.

I'll close here, since #48 is enough for tracking the problem.

authors: dginev rspeer


text:
When searching for offline devices, the return is 0, but there is actually one device

Thanks for your feedback. the issue has been resolved

repo: dgiot/dgiot


text:
Support for ring two step verification?

is it even possible to support ring's two step verification?

I'm guessing it would be possible if we took an approach like https://github.com/KhaosT/homebridge-nest-cam#how-to-get-access-token.  The main issue is that you need to be in the loop every time a new token is required by the plugin.  There should be a token refresh endpoint, but if your homebridge was offline for a day or more, your token would probably expire and require you to update your configuration file with a new manually fetched token. I'm all for 2fa, so i'd be happy to review a PR if someone has time to work on this.

repo: dgreif/ring-alarm


text:
Email Notification template not using tokens when in Markdown mode?

Describe the bug
Hiya,
I have a notification body of:
{diff}

`# [FULL]({diff_url})`

{diff_full}

# [URL]({watch_url})

with "markdown" as the format.
However, I don't see links appearing in my emails. Am I doing something wrong, or is there a bug, or are my expectations not aligned? I'm expecting to
see links in my email like this:
FULL [{diff_url}]

but, actually, I see:

# [FULL]({diff_url})

Version
v0.39.21.1

@blippercop thats because its fixed after the latest version and the fix is in head or:dev latest docker


text:
Tilføj metadata

Tilføj metadata så vi kan få en ordenlig beskrivelse på google:

#11 også relateret til denne

@heidipi ved du noget om SEO? :')

Jeg har tilføjet en meta description. Feel free to change it

Det er perfekt

authors: dhil frmi heidipi

repo: dhil/mandriljulekalender


text:
new test theme

Testing theme preview generation on comments for PRs

Theme preview generator
title-color: #00bbff
icon-color: #2ddaaa
text-color: #ffffff
bg-color: #050f2c

Theme preview generator
title-color: #00bbff
icon-color: #2ddaaa
text-color: #ffffff
bg-color: #050f2c

Theme preview generator
title-color: #00bbff
icon-color: #2ddaaa
text-color: #ffffff
bg-color: #050f2c

New theme preview in comments is working properly, so closing this PR.

Theme preview generator
title-color: #00bbff
icon-color: #2ddaaa
text-color: #ffffff
bg-color: #050f2c

authors: VatsalSy dhyeythumar

repo: dhyeythumar/youtube-stats-card


text:
CreateOrUpdateProduct execute successfully but Ozon says Key fields missing

send a whole CreateOrUpdateProductParams object :
{Items:[{"attributes":[{"complex_id":0,"id":4384,"values":[{"dictrionary_value_id":0,"value":"Упаковка, комплект ламп, гарантийний талон."}]},{"complex_id":0,"id":8229,"values":[{"dictrionary_value_id":367249974,"value":"Лампа автомобильная"}]},{"complex_id":0,"id":7236,"values":[{"dictrionary_value_id":0,"value":"LZ8ULTRA"}]},{"complex_id":0,"id":8383,"values":[{"dictrionary_value_id":0,"value":"13000"}]},{"complex_id":0,"id":9024,"values":[{"dictrionary_value_id":0,"value":"91132"}]},{"complex_id":0,"id":9048,"values":[{"dictrionary_value_id":0,"value":"Z8 ULTRA NANO-LED"}]},{"complex_id":0,"id":7199,"values":[{"dictrionary_value_id":61753,"value":"Алюминий"}]},{"complex_id":0,"id":4180,"values":[{"dictrionary_value_id":0,"value":"LED лампа Z8 Ultra nano-led с тройной системой охлаждения/100w/5000k/комплект, для автомобильных фар/ HB4"}]},{"complex_id":0,"id":22241,"values":[{"dictrionary_value_id":971405507,"value":"Для ближнего/дальнего света"}]},{"complex_id":0,"id":4191,"values":[{"dictrionary_value_id":0,"value":"Ручная сборка LED-лампы, высокотехнологичные диоды, инновационная система охлаждения.\u003cbr/\u003e\u003cbr/\u003eМодель Z8 имеет тройную систему охлаждения \u003cbr/\u003e\u003cbr/\u003e-Модель: Z8\u003cbr/\u003e\u003cbr/\u003e-Мощность: 100W\u003cbr/\u003e\u003cbr/\u003e-Световой поток: 13000lumens\u003cbr/\u003e\u003cbr/\u003e-Цветовая температура: 5000K\u003cbr/\u003e\u003cbr/\u003e-Чип: CSP+USA\u003cbr/\u003e\u003cbr/\u003e-Материал: Авиационный алюминий\u003cbr/\u003e\u003cbr/\u003e-Влагозащита: IP68\u003cbr/\u003e\u003cbr/\u003e-Гарантия: 24 месяца\u003cbr/\u003e\u003cbr/\u003eПодключение: штатное\u003cbr/\u003e\u003cbr/\u003eЦена за комплект\u003cbr/\u003e\u003cbr/\u003eПремиум сегмент\u003cbr/\u003e\u003cbr/\u003e- Прирост света на 90%;\u003cbr/\u003e\u003cbr/\u003e- Штатная установка;\u003cbr/\u003e\u003cbr/\u003e- Подходит для установки ближнего, дальнего;\u003cbr/\u003e\u003cbr/\u003e- Минимальное нагревание за счет тройного охлаждения;\u003cbr/\u003e\u003cbr/\u003e- Мы предоставляем гарантию 2 года, по сравнению с другими компаниями;\u003cbr/\u003e\u003cbr/\u003e- Модель Z8 от производителя "LEDOVЫЙ" имеет более качественную сборку, что дает возможность служить гораздо дольше, чем бюджетный аналог.\u003cbr/\u003e\u003cbr/\u003eВнимание! При использовании ламп в фарах без крышек (если предусмотрено заводом изготовителем), гарантия не распространяется.\u003cbr/\u003e\u003cbr/\u003eОбратите внимание, что мы не гарантируем 100% совместимость ламп с вашим автомобилем. В редком случае лампы могут работать некорректно. Встроенная обманка не способна обойти все бортовые компьютеры. Это не является гарантийным событием и лампы можно вернуть в магазин как не подошедший товар. Также для обхода требовательного БК мы рекомендуем оснащать лампы специальной обманкой\u003cbr/\u003e\u003cbr/\u003eВ Головной свет применяется кулерные модели (активное охлаждение)\u003cbr/\u003e\u003cbr/\u003eДля противотуманных фар радиаторные модели (пассивное охлаждение)\u003cbr/\u003e\u003cbr/\u003eLED Лампа нового поколения Z8 Ultra благодаря своему исполнению в плане конструктива и инженерных решений это лучший вариант качественных ламп с оправданной ценой в отличии от именитых конкурентов. Срок службы светодиодной лампы может составлять до 10 лет, а его энергопотребление во много раз ниже «классики»\u003cbr/\u003e\u003cbr/\u003eВ автомобилях все эти преимущества особенно актуальны, так как чем ниже потребление тока, тем заметней снижается нагрузка на аккумулятор. Да и менять перегоревшие лампы придётся гораздо реже.\u003cbr/\u003e\u003cbr/\u003eПостоянный прирост на 100+ % за счёт диодных ламп Z8 Ultra, почему именно постоянные? Потому что наша led лампа обладает 3-ой системой охлаждения, первое — это активный кулер, который крутится внутри радиатора, второе - 2 алюминиевые трубки (по всей длине диодной платы), в которых циркулирует жидкость, охлаждая дорожку, на которой расположены диоды. И третье охлаждение — это алюминий, который отводит тепло от диодов. Все эти свойства обеспечивают диоду постоянную рабочую температуру за счёт чего он не нагревается и не теряет своих свойств, светит ярче и работают дольше. У нашей модели Z8 Ultra максимальная гарантия - 2 года. \u003cbr/\u003e\u003cbr/\u003eДиодные лампы для авто под разные автомобили имеют свои цоколя, к примеру лед лампы h7\u003cbr/\u003e\u003cbr/\u003eили лед лампы h4. У нас вы найдёте практический весь спектр цоколей на все представленные модели.\u003cbr/\u003e\u003cbr/\u003eЛампа автомобильная может располагаться и в головном свете, дальний и ближний.\u003cbr/\u003e\u003cbr/\u003eЛампочки светодиодные так же устанавливаются в салонном освещении, в багажнике, в освещении номерных знаков и так далее.\u003cbr/\u003e\u003cbr/\u003eВ нашем магазине LEDOVЫЙ вы найдёте любой тип led ламп от головного света до, к примеру линзованные лед лампы, переходник для led ламп, колпачки для фар, би модули, линзы и любые лампочки в фары."}]},{"complex_id":0,"id":7206,"values":[{"dictrionary_value_id":41233,"value":"Легковые автомобили"},{"dictrionary_value_id":41240,"value":"Внедорожники"},{"dictrionary_value_id":41230,"value":"Грузовые автомобили и автобусы"},{"dictrionary_value_id":41232,"value":"Коммерческий транспорт"},{"dictrionary_value_id":41237,"value":"Снегоходы"},{"dictrionary_value_id":41234,"value":"Мотоциклы"},{"dictrionary_value_id":41231,"value":"Квадроциклы"}]},{"complex_id":0,"id":4385,"values":[{"dictrionary_value_id":0,"value":"24"}]},{"complex_id":0,"id":4400,"values":[{"dictrionary_value_id":40875,"value":"12 В"}]},{"complex_id":0,"id":6317,"values":[{"dictrionary_value_id":1896,"value":"Светодиодная"}]},{"complex_id":0,"id":6318,"values":[{"dictrionary_value_id":0,"value":"2"}]},{"complex_id":0,"id":4389,"values":[{"dictrionary_value_id":90296,"value":"Китай"}]},{"complex_id":0,"id":85,"values":[{"dictrionary_value_id":970888017,"value":"LEDOVЫЙ"}]},{"complex_id":0,"id":6319,"values":[{"dictrionary_value_id":0,"value":"100"}]},{"complex_id":0,"id":8386,"values":[{"dictrionary_value_id":0,"value":"5000"}]},{"complex_id":0,"id":11650,"values":[{"dictrionary_value_id":0,"value":"1"}]},{"complex_id":0,"id":10100,"values":[{"dictrionary_value_id":0,"value":"false"}]},{"complex_id":0,"id":11794,"values":[{"dictrionary_value_id":970860783,"value":"safe"}]},{"complex_id":0,"id":22074,"values":[{"dictrionary_value_id":0,"value":"false"}]},{"complex_id":0,"id":9790,"values":[{"dictrionary_value_id":0,"value":"false"}]},{"complex_id":0,"id":22232,"values":[{"dictrionary_value_id":971400201,"value":"8539520009 - Лампы светодиодные (led), прочие"}]},{"complex_id":0,"id":22387,"values":[{"dictrionary_value_id":971461138,"value":"Auto\u0026Moto/Авто и мото запчасти/Автомобильная оптика/Лампы и комплектующие"}]},{"complex_id":0,"id":22806,"values":[{"dictrionary_value_id":971400201,"value":"8539520009 - Лампы светодиодные (led), прочие"}]},{"complex_id":0,"id":9461,"values":[{"dictrionary_value_id":349823813,"value":"Лампы и комплектующие"}]},{"complex_id":0,"id":12978,"values":[{"dictrionary_value_id":970978730,"value":"HB4"}]},{"complex_id":0,"id":10015,"values":[{"dictrionary_value_id":0,"value":"false"}]}],"barcode":"","description_category_id":17028756,"color_image":"","complex_attributes":[{"attributes":[{"complex_id":100001,"id":21840,"values":[{"dictrionary_value_id":0,"value":"01G9C3B7R6DTV02TKV3XB51SZX"}]},{"complex_id":100001,"id":21838,"values":[{"dictrionary_value_id":0,"value":"https://cdn1.ozone.ru/s3/video/cover/01G9C3B7R6DTV02TKV3XB51SZX.jpg"}]},{"complex_id":100001,"id":21839,"values":[{"dictrionary_value_id":0,"value":"https://v.ozone.ru/vod/video-2/01G9C3B7R6DTV02TKV3XB51SZX/master.m3u8"}]},{"complex_id":100001,"id":21841,"values":[{"dictrionary_value_id":0,"value":"https://v.ozone.ru/vod/video-2/01G9C3B7R6DTV02TKV3XB51SZX/asset_2.mp4"}]},{"complex_id":100001,"id":21837,"values":[{"dictrionary_value_id":0,"value":"Обзор"}]}]},{"attributes":[{"complex_id":100002,"id":21843,"values":[{"dictrionary_value_id":0,"value":"https://v.ozone.ru/vod/video-15/01GYZ36FV4SM54WY86RV71DFHZ/asset_2_h264.mp4"}]},{"complex_id":100002,"id":21844,"values":[{"dictrionary_value_id":0,"value":"01GYZ36FV4SM54WY86RV71DFHZ"}]},{"complex_id":100002,"id":21845,"values":[{"dictrionary_value_id":0,"value":"https://v.ozone.ru/vod/video-15/01GYZ36FV4SM54WY86RV71DFHZ/asset_2_h264.mp4"}]},{"complex_id":100002,"id":21846,"values":[{"dictrionary_value_id":0,"value":"https://v.ozone.ru/vod/video-15/01GYZ36FV4SM54WY86RV71DFHZ/master.m3u8"}]},{"complex_id":100002,"id":21842,"values":[{"dictrionary_value_id":0,"value":"https://cdn1.ozone.ru/s3/video-15/01GYZ36FV4SM54WY86RV71DFHZ/cover/cover.jpg"}]}]},{"attributes":[{"complex_id":100003,"id":22917,"values":[{"dictrionary_value_id":971491651,"value":"Golf, VI (2008 - 2012) Хэтчбек 3 дв."}]},{"complex_id":100003,"id":22918,"values":[{"dictrionary_value_id":971520309,"value":"MultiFuel 1.6 MT (102 л.с.) BSE,BSF,CCSA,CMXA"}]},{"complex_id":100003,"id":22916,"values":[{"dictrionary_value_id":58175,"value":"Volkswagen"}]}]}],"depth":120,"dimension_unit":"mm","geo_names":[],"height":50,"images":["https://cdn1.ozone.ru/s3/multimedia-9/6532430541.jpg","https://cdn1.ozone.ru/s3/multimedia-a/6532430542.jpg","https://cdn1.ozone.ru/s3/multimedia-8/6532430540.jpg","https://cdn1.ozone.ru/s3/multimedia-7/6532430539.jpg","https://cdn1.ozone.ru/s3/multimedia-b/6532430543.jpg","https://cdn1.ozone.ru/s3/multimedia-f/6532409451.jpg"],"primary_image":"https://cdn1.ozone.ru/s3/multimedia-p/6715190221.jpg","images_360":[],"name":"LED лампа Z8 Ultra nano-led с тройной системой охлаждения/100w/5000k/комплект, для автомобильных фар/ HB4","offer_id":"91132","currency_code":"CNY","old_price":"100","pdf_list":[],"premium_price":"70","price":"80","service_type":"IS_CODE_SERVICE","vat":"0.0","weight":350,"weight_unit":"g","width":175}]}
task status can be "imported" ,but in ozon backend, there is an error message:
serious
Please correct the error, otherwise the product will not be updated. Showing cards without recent changes on Ozon
Model Name - Required attribute is not filled in. Occasionally we update required attributes or add new ones. Please edit the product or upload a new XLS template with the current attributes.
Part Number (Manufacturer's Article Number) - Required attribute is not filled in. Occasionally we update required attributes or add new ones. Please edit the product or upload a new XLS template with the current attributes.
Brand - Required attribute is not filled in. Occasionally we update required attributes or add new ones. Please edit the product or upload a new XLS template with the current attributes.
Type - Required attribute is not filled in. Occasionally we update required attributes or add new ones. Please edit the product or upload a new XLS template with the current attributes.

Hi! Thank you for your feedback and reporting a bug. I will take a look at the problem and come back with response.

I'm back with some info
I executed a request through this API and console on official Ozon API website and I got the same result, which means mistake is somewhere in your code.
How does it work?
When you execute CreateOrUpdateProduct, Ozon API doesn't check required parameters to create or update a product. The parameters are actually checked when it tries to do the task. And then it says you haven't provided some of the required parameters.
Well, this is what I've found. Please try to fill some other fields and give me feedback if the problem is solved

Closing this issue as been solved. If you still have issues, please feel free to reopen this issue

Continued in #68

Please release a new version
2024年2月11日 07:38，Kirill @.@.>> 写道：
Closed #67https://github.com/diPhantxm/ozon-api-client/issues/67 as completed.
—
Reply to this email directly, view it on GitHubhttps://github.com/diPhantxm/ozon-api-client/issues/67#event-11765892064, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGM46ICFIGU2SR5QVREI2JDYTAAHNAVCNFSM6AAAAABCTHF37OVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRG43DKOBZGIYDMNA.
You are receiving this because you authored the thread.Message ID: @.***>

Please release a new version 2024年2月11日 07:38，Kirill @.@.>> 写道： Closed #67<#67> as completed. — Reply to this email directly, view it on GitHub<#67 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGM46ICFIGU2SR5QVREI2JDYTAAHNAVCNFSM6AAAAABCTHF37OVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRG43DKOBZGIYDMNA. You are receiving this because you authored the thread.Message ID: @.***>

I will try to update library according to these recent updates and release a new version

copy that, thanks
2024年2月11日 17:58，Kirill @.@.>> 写道：
Please release a new version 2024年2月11日 07:38，Kirill @.@.>> 写道： Closed #67https://github.com/diPhantxm/ozon-api-client/issues/67<#67https://github.com/diPhantxm/ozon-api-client/issues/67> as completed. — Reply to this email directly, view it on GitHub<#67 (comment)https://github.com/diPhantxm/ozon-api-client/issues/67#event-11765892064>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGM46ICFIGU2SR5QVREI2JDYTAAHNAVCNFSM6AAAAABCTHF37OVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRG43DKOBZGIYDMNA. You are receiving this because you authored the thread.Message ID: @.***>
I will try to update library according to these recenthttps://docs.ozon.ru/api/seller/en/#section/February-9-2024 updates and release a new version
—
Reply to this email directly, view it on GitHubhttps://github.com/diPhantxm/ozon-api-client/issues/67#issuecomment-1937499447, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGM46IBKS7VR2HHXS5U3NO3YTCI57AVCNFSM6AAAAABCTHF37OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZXGQ4TSNBUG4.
You are receiving this because you authored the thread.Message ID: @.***>

copy that, thanks 2024年2月11日 17:58，Kirill @.@.>> 写道： Please release a new version 2024年2月11日 07:38，Kirill @.@.>> 写道： Closed #67<#67><#67https://github.com/diPhantxm/ozon-api-client/issues/67> as completed. — Reply to this email directly, view it on GitHub<#67 (comment)<#67 (comment)>>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGM46ICFIGU2SR5QVREI2JDYTAAHNAVCNFSM6AAAAABCTHF37OVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRG43DKOBZGIYDMNA. You are receiving this because you authored the thread.Message ID: @.> I will try to update library according to these recenthttps://docs.ozon.ru/api/seller/en/#section/February-9-2024 updates and release a new version — Reply to this email directly, view it on GitHub<#67 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGM46IBKS7VR2HHXS5U3NO3YTCI57AVCNFSM6AAAAABCTHF37OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZXGQ4TSNBUG4. You are receiving this because you authored the thread.Message ID: @.>

Published

authors: JoeyFrancisTribbiani diPhantxm

repo: diPhantxm/ozon-api-client


text:
Docs unavailable

Hi
With the website down, the linked documentation is not available anymore. Can you copy it into the project or the wiki, please?
Also what's the state of the project, will it continue in the future?
regards, Daniel

hi @Dahie thank you so much for keeping an eye on this one, I just updated the url for the documentation, just in case is (this one)[http://diablourbano.com/grapevine/]
Sorry for the delay in the response, I'm trying to get time to fix this kind of issues.
Anyway, about the state of the project, I'm really happy to know there're some people who at least had considered to check it, however if you check (grape)[http://www.ruby-grape.org] you'll find they have included a lot of functionality which makes this project outdated. If you find any bug please let me know, so I can fix it, but new features or version updates, honestly, I don't think they will appear.
Thanks again, knowing someone saw this made my day :)

You're welcome, thank you! :)

authors: Dahie diablourbano

repo: diablourbano/grapevine


text:
pragmatic_segmenter installing problem

gem install pragmatic_segmenter
Successfully installed pragmatic_segmenter-0.3.22
Parsing documentation for pragmatic_segmenter-0.3.22
Done installing documentation for pragmatic_segmenter after 0 seconds
1 gem installed
But it does not install:
sevilay@sevilay-linux:~$ apt-cache policy pragmatic_segmenter
N: Unable to locate package pragmatic_segmenter
Please anyone could tell me what is the problem?

Hi @sevilaybayatli, I'm responding to your comment here: https://github.com/diasks2/pragmatic_segmenter/pull/68#issuecomment-762462583
It seems like your system should have the gem installed properly. gem install is different from apt install, so instead of using apt-cache, use gem list to look for the package.
As for your code, if you re-run it now, I think you should have no error when you require pragmatic_segmenter in your code.

Hi @sevilaybayatli, I'm responding to your comment here: https://github.com/diasks2/pragmatic_segmenter/pull/68#issuecomment-762462583
It seems like your system should have the gem installed properly. gem install is different from apt install, so instead of using apt-cache, use gem list to look for the package.
As for your code, if you re-run it now, I think you should have no error when you require pragmatic_segmenter in your code.

Hi @alextsui05,
:~$ gem list
*** LOCAL GEMS ***
bigdecimal (1.2.8)
did_you_mean (1.0.0)
io-console (0.4.5)
json (1.8.3)
minitest (5.8.3)
net-telnet (0.1.1)
power_assert (0.2.6)
pragmatic (0.1.1)
pragmatic_segmenter (0.3.22, 0.3.18)
psych (2.0.17)
rake (10.4.2)
rdoc (4.2.1)
test-unit (3.1.5)
unicode (0.4.4.4)
It seems I have pragmatic-segmenter, I don't understand why  got that error then:(

Hi @alextsui05,
:~$ gem list
*** LOCAL GEMS ***
bigdecimal (1.2.8)
did_you_mean (1.0.0)
io-console (0.4.5)
json (1.8.3)
minitest (5.8.3)
net-telnet (0.1.1)
power_assert (0.2.6)
pragmatic (0.1.1)
pragmatic_segmenter (0.3.22, 0.3.18)
psych (2.0.17)
rake (10.4.2)
rdoc (4.2.1)
test-unit (3.1.5)
unicode (0.4.4.4)
It seems I have pragmatic-segmenter, I don't understand why  got that error then:(

Is this solved with the newest version: https://github.com/diasks2/pragmatic_segmenter/pull/68 ?

Yeah it solved.

Solved!


text:
Unable to have projects visible on ethereal nexus dashboard

Hi Team,
We are using the ethereal nexus with docker image version 1.0.2 but now our projects are not visible on the dashboard. Getting an error "There's an issue with the project records." The projects are getting created in database and can be seen there. But not on the dashboard. This was present earlier in the image 1.26.0 but after the upgrade doesn't work.
We have made some adjustments in the database with new table environment table added.

Can someone help us on this?

This issue is solved and can be closed. It was solved by running the updated script on database for schema changes and deleted all the old projects.

repo: diconium/ethereal-nexus


text:
注册 BpmnAdapter 后无法渲染初始数据

问题描述
http://logic-flow.org/examples/#/extension/adapter 官网代码在本地测试，  注册 LogicFlow.use(BpmnAdapter); 后无法渲染初始数据。删除它才能渲染初始数据。
最简复现demo ：代码来源官网examples extension/adapter/index.tsx
const data = {
  nodes: [
    {
      id: 10,
      type: 'rect',
      x: 150,
      y: 70,
      text: '矩形',
    },
  ],
};

let lf: LogicFlow;

export default function AdapterExample() {
  useEffect(() => {
    LogicFlow.use(BpmnAdapter); // 删掉这个才能显示

    lf = new LogicFlow({
      container: document.querySelector('#graph') as HTMLElement,
      stopScrollGraph: true,
      stopZoomGraph: true,
    });

    lf.render(data);
  }, []);

  return (
    <>

    </>
  );
}

因为adapter的用处就是数据格式转换的，用的adapter，就必须使用adapter支持的这种数据格式了。BpmnAdapter需要你用bpmn格式的数据进行渲染

因为adapter的用处就是数据格式转换的，用的adapter，就必须使用adapter支持的这种数据格式了。BpmnAdapter需要你用bpmn格式的数据进行渲染

我用了 bpmn xml 格式数据传进去，bpmnXmlAdapter 也无法正常加载。有demo渲染bpmn xml嘛？

bpmnAdapter目前只兼容了bpmnElement这些元素，其它元素还不支持。建议参考bpmnAdapter编写你们自己项目的adapter

解决了吗？我也遇到这个我问题了

如何把这个初始的数据转换成bpmn格式的数据？

踩了一天的坑，我来回答这个问题。只需要使用lf.renderRawData(data)就可以实现。

authors: luohaijun123 towersxu wghglory yangyingnan

repo: didi/LogicFlow


text:
gradle clean iR编译到最后失败

Installing APK 'app-release.apk' on 'HUAWEI M2-A01W - 5.1.1' for app:release
Unable to install C:\Users\lc\Desktop\VirtualAPK-master\app\build\outputs\apk\app-release.apk
com.android.ddmlib.InstallException: Failed to install all
at com.android.ddmlib.SplitApkInstaller.install(SplitApkInstaller.java:91)
at com.android.ddmlib.Device.installPackages(Device.java:901)
at com.android.builder.testing.ConnectedDevice.installPackages(ConnectedDevice.java:119)
at com.android.build.gradle.internal.tasks.InstallVariantTask.install(InstallVariantTask.java:134)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:75)
at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.doExecute(AnnotationProcessingTaskFactory.java:228)
at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:221)
at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:210)
at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:621)
at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:604)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:80)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:61)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:46)
at org.gradle.api.internal.tasks.execution.PostExecutionAnalysisTaskExecuter.execute(PostExecutionAnalysisTaskExecuter.java:35)
at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:66)
at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)
at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:52)
at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)
at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:53)
at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:203)
at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:185)
at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.processTask(AbstractTaskPlanExecutor.java:66)
at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.run(AbstractTaskPlanExecutor.java:50)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor.process(DefaultTaskPlanExecutor.java:25)
at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter.execute(DefaultTaskGraphExecuter.java:110)
at org.gradle.execution.SelectedTaskExecutionAction.execute(SelectedTaskExecutionAction.java:37)
at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:37)
at org.gradle.execution.DefaultBuildExecuter.access$000(DefaultBuildExecuter.java:23)
at org.gradle.execution.DefaultBuildExecuter$1.proceed(DefaultBuildExecuter.java:43)
at org.gradle.execution.DryRunBuildExecutionAction.execute(DryRunBuildExecutionAction.java:32)
at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:37)
at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:30)
at org.gradle.initialization.DefaultGradleLauncher$4.run(DefaultGradleLauncher.java:153)
at org.gradle.internal.Factories$1.create(Factories.java:22)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:91)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:53)
at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:150)
at org.gradle.initialization.DefaultGradleLauncher.access$200(DefaultGradleLauncher.java:32)
at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:98)
at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:92)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:91)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:63)
at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:92)
at org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:83)
at org.gradle.launcher.exec.InProcessBuildActionExecuter$DefaultBuildController.run(InProcessBuildActionExecuter.java:99)
at org.gradle.tooling.internal.provider.ExecuteBuildActionRunner.run(ExecuteBuildActionRunner.java:28)
at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:48)
at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:30)
at org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:81)
at org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:46)
at org.gradle.launcher.exec.DaemonUsageSuggestingBuildActionExecuter.execute(DaemonUsageSuggestingBuildActionExecuter.java:51)
at org.gradle.launcher.exec.DaemonUsageSuggestingBuildActionExecuter.execute(DaemonUsageSuggestingBuildActionExecuter.java:28)
at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:43)
at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:173)
at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:239)
at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:212)
at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:35)
at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)
at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:205)
at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:169)
at org.gradle.launcher.Main.doAction(Main.java:33)
at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:55)
at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:36)
at org.gradle.launcher.GradleMain.main(GradleMain.java:23)
09:44:25 E/178381408: Error while uploading app-release.apk : Unknown failure ([CDS]close[0])
:app:installRelease FAILED> Building 97% > :app:installRelease
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:installRelease'.

com.android.builder.testing.api.DeviceException: com.android.ddmlib.InstallException: Failed to install all

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED
gradle版本2.14.1  机型HUAWEI M2-A01W - 5.1.1

看log已经编译出了apk，在install的时候出错了，可以试试手动安装看看有没有问题

repo: didi/VirtualAPK


text:
 better-scroll 1.9.1 + scroll + slide

Please make sure these boxes are checked before submitting your PR, thank you!

[x] Make sure you follow DiDi's contributing guide.
[x] Make sure you are merging your commits to dev branch.
[x] Add some descriptions and refer relative issues for you PR.

Codecov Report

Merging #139 into dev will increase coverage by 0.14%.
The diff coverage is 93.33%.

@@            Coverage Diff             @@
##              dev     #139      +/-   ##
==========================================
+ Coverage   89.02%   89.16%   +0.14%
==========================================
  Files          89       89
  Lines        1640     1662      +22
  Branches      227      236       +9
==========================================
+ Hits         1460     1482      +22
+ Misses         99       94       -5
- Partials       81       86       +5

Impacted Files
Coverage Δ

src/components/slide/slide.vue
69.87% <ø> (ø)
:arrow_up:

src/components/scroll/scroll.vue
89.71% <93.33%> (+2.66%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a9cf01c...30ef0f9. Read the comment docs.

Travis tests have failed
Hey @AmyFoxFN,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.
Node.js: 6

     npm test

> cube-ui@1.6.1 test /home/travis/build/didi/cube-ui
> npm run unit && npm run codecov

> cube-ui@1.6.1 unit /home/travis/build/didi/cube-ui
> cross-env BABEL_ENV=test karma start test/unit/karma.conf.js --single-run

(node:4074) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56
parseQuery() will be replaced with getOptions() in the next major version of loader-utils.
29 03 2018 06:24:13.058:INFO [karma]: Karma v1.7.1 server started at http://0.0.0.0:9876/
29 03 2018 06:24:13.060:INFO [launcher]: Launching browser PhantomJS_mobile with unlimited concurrency
29 03 2018 06:24:13.068:INFO [launcher]: Starting browser PhantomJS
29 03 2018 06:24:13.964:INFO [PhantomJS 2.1.1 (Linux 0.0.0)]: Connected on socket WJvYncLOwwNb9A9IAAAA with id 40771057
PhantomJS 2.1.1 (Linux 0.0.0) INFO LOG: 'You are running Vue in development mode.
Make sure to turn on production mode when deploying for production.
See more tips at https://vuejs.org/guide/deployment.html'

  ActionSheet
    ActionSheet.vue
      ✓ use
      ✓ should render correct contents
      ✓ should render correct contents - no data
      ✓ should render correct contents - picker style
      ✓ should trigger events
    ActionSheet API
      ✓ $createActionSheet API

  Button.vue
    ✓ use
    ✓ should render correct contents
    ✓ props
    ✓ events-called
    ✓ events-no-called

  CascadePicker
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents when use alias
    ✓ should trigger events
    ✓ should call methods
    ✓ $updateProps
    ✓ should add warn log when single is true

  CheckboxGroup.vue
    ✓ use
    ✓ should render correct contents (horizontal=false)
    ✓ should render correct contents (horizontal=true)
    ✓ should change v-model value

  Checkbox.vue
    ✓ use
    ✓ should render correct contents
    ✓ should toggle v-model value

  Dialog
    Dialog.vue
      ✓ use
      ✓ should render correct contents - icon
      ✓ should render correct contents - title
      ✓ should render correct contents - alert
      ✓ should render correct contents - confirm
      ✓ should render correct contents - confirmBtn/cancelBtn
      ✓ should trigger events
      ✓ should not trigger events when btn is disabled
    Dialog API
      ✓ $createDialog API

  IndexList
    IndexList.vue
      ✓ use
      ✓ should render correct contents
      ✗ should trigger events
	expected spy to have been called with arguments { name: "鞍山市", value: 3 }

      ✓ should fixed title
      ✓ run normal when group or item undefined
      ✓ should handle condition of unexpected param

  Input.vue
    ✓ use
    ✓ should render correct contents
    ✓ should not show clear button when no text
    ✓ should show clear button when has text
    ✓ value should be empty when clear button clicked
    ✓ should support more native props
    ✓ should show password eye and work correctly

  Loading.vue
    ✓ use
    ✓ should render correct contents - no size
    ✓ should render correct contents - with size

  Picker
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents when use alias
    ✓ should trigger events
    ✓ should refill correct
    ✓ should add warn log when single is true
    ✓ setData when picker is invisible
    ✓ setData when picker is visible

  Popup
    Popup.vue
      ✓ use
      ✓ should render correct contents - no type
      ✓ should render correct contents
      ✓ events
    Popup API
      ✓ $createPopup API

  Radio.vue
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents - horizontal
    ✓ should toggle v-model value

  Rate.vue
    ✓ use
    ✓ should render correct contents
    ✓ should trigger change event
    ✓ should trigger change event with click

  Scroll
    ✓ use
    ✓ should correct by default
    ✓ should render correct contents
    ✓ should trigger pullingDown
    ✓ should not trigger pullingDown
    ✓ should trigger pullingUp
    ✓ should not trigger pullingUp
    ✓ should trigger click
    ✓ should trigger other events
    ✓ should call correct method

  SegmentPicker
    ✓ use
    ✓ should render correct contents
    ✓ should correct by default
    ✓ should trigger events
    ✓ $updateProps
    ✓ should add warn log when single is true

  Select.vue
    ✓ use
    ✓ should render correct contents
    ✓ should trigger events

  Slide.vue
    ✓ use
    ✓ should render correct contents
    ✓ should trigger change event

  Swipe
    ✓ use
    ✓ should render correct contents
    ✓ should shrink if the swipe width not enough
    ✓ should shrink if the last moving direction is right
    ✓ should shrink and not moved if the duration is more than momentumLimitTime and moving distance is less than momentumLimitDistance
    ✓ should shrink and not moved if y-axis distance is more than x-axis distance
    ✓ should grow if the swipe width enough
    ✓ should grow if the duration is less than momentumLimitTime and moving distance is more than momentumLimitDistance
    ✓ should not swipe out of the boundaries when swiping left
    ✓ should not swipe out of the boundaries when swiping right
    ✓ should trigger events
    ✓ should shrink if another swipe item active
    ✓ should do nothing if active the same swipe item
    ✓ should call refresh if the btns prop has changed
    ✓ should use default props if do not pass any prop

  Switch
    ✓ use
    ✓ should render correct contents
    ✓ should toggle v-model value

  Textarea.vue
    ✓ use
    ✓ should render correct contents
    ✓ should not expand when blur
    ✓ should expand when focus, fold when blur
    ✓ should has remain when focus
    ✓ should change value
    ✓ should support more native props

  TimePicker
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents - no showNow
    ✓ should trigger events
    ✓ should add warn log when sigle is true

  Tip.vue
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents with offset[X]
    ✓ should be hidden after clicked content
    ✓ should be hidden after clicked close button

  Toast
    Toast.vue
      ✓ use
      ✓ should render correct contents - no type
      ✓ should render correct contents - time 0
      ✓ should render correct contents - with type
    Toast API
      ✓ $createToast API

  Upload.vue
    ✓ use
    ✓ should render correct contents
    ✓ should add files & upload
    ✓ should remove file
    ✓ should start & pause upload
    ✓ should retry upload
    ✓ should trigger events

  validator.vue
    ✓ use
    ✓ should render correct contents - invalid

  rules
    ✓ should be valid - no rule
    ✓ should be valid - unstated rule
    ✓ should be invalid - require: array
    ✓ should be invalid - type: string
    ✓ should be valid - type: string
    ✓ should be invalid - type: number
    ✓ should be valid - type: number
    ✓ should be invalid - type: array
    ✓ should be valid - type: array
    ✓ should be invalid - type: date
    ✓ should be valid - type: date
    ✓ should be invalid - type: email
    ✓ should be valid - type: email
    ✓ should be invalid - type: tel
    ✓ should be valid - type: tel
    ✓ should be invalid - type: url
    ✓ should be valid - type: url
    ✓ should be invalid - min: string
    ✓ should be valid - min: number
    ✓ should be valid - max: string
    ✓ should be invalid - min: number
    ✓ should be valid - min: string
    ✓ should be invalid - min: number
    ✓ should be invalid - notWhitespace
    ✓ should be invalid - pattern
    ✓ should be invalid - custom

  methods
    ✓ should add customized rule and message
    ✓ should rewrite raw type
    ✓ should change the language of default message

PhantomJS 2.1.1 (Linux 0.0.0): Executed 171 of 171 (1 FAILED) (27.19 secs / 26.575 secs)
TOTAL: 1 FAILED, 170 SUCCESS

1) should trigger events
     IndexList IndexList.vue
     expected spy to have been called with arguments { name: "鞍山市", value: 3 }

=============================== Coverage summary ===============================
Statements   : 94.18% ( 1554/1650 )
Branches     : 77.95% ( 587/753 )
Functions    : 94.38% ( 151/160 )
Lines        : 94.18% ( 1554/1650 )
================================================================================

npm ERR! Linux 4.14.12-041412-generic
npm ERR! argv "/home/travis/.nvm/versions/node/v6.14.0/bin/node" "/home/travis/.nvm/versions/node/v6.14.0/bin/npm" "run" "unit"
npm ERR! node v6.14.0
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! cube-ui@1.6.1 unit: `cross-env BABEL_ENV=test karma start test/unit/karma.conf.js --single-run`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the cube-ui@1.6.1 unit script 'cross-env BABEL_ENV=test karma start test/unit/karma.conf.js --single-run'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the cube-ui package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     cross-env BABEL_ENV=test karma start test/unit/karma.conf.js --single-run
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs cube-ui
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls cube-ui
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/travis/build/didi/cube-ui/npm-debug.log
npm ERR! Test failed.  See above for more details.

authors: AmyFoxFN TravisBuddy codecov-io

repo: didi/cube-ui


text:
screenshot

What's your question?
It does not show me the image of what the player is playing

Hello @jovalois
Do you installed the add-on on the target player?
bash <(curl -sL https://git.io/Jf900)
Best
didiatworkz

If it was installed and it does not generate an error but it still seems that it is not installed, I am attaching an image

Hello @jovalois
So let me get this straight...
You have also logged into player 192.168.1.82 via ssh and executed the command: bash <(curl -sL https://git.io/Jf900)
If this is installed correctly, then a script must be here:
/usr/bin/screenshot.sh
a crontab can be found here: sudo crontab -e
sleep 20 && /usr/bin/screenshot.sh >> /var/log/screenshot.log 2>1
and this command must also work: raspi2png --help
If one of them doesn't fit, then you have to install the whole thing again and send me the complete output of the installation.
Best
didiatworkz
PS: 192.168.1.82:9020/screen/screenshot.png is the address to check, as soon as it is reachable, the image is retrieved

No response from author - Issue will be closed

authors: didiatworkz jovalois

repo: didiatworkz/screenly-ose-monitor


text:
Let to pass an arbitrary number of cyphers to PublicKey.Add

PublicKey.Add accepts now an arbitrary number of *Cyphers. Previously, it was possible to add only two *Cypher instances and it was quite unwieldy for a lot of use cases.
The current implementation is backward compatible. It's still possible to pass just two *Cypher arguments, so every project referencing the library will observe no compilation issues.
// backward-compatibility
cypherA := privateKey.Add(cypher1, cypher2)

// you can pass any number of cyphers now
cypherB := privateKey.Add(cypher1, cypher2, cypher3, cypher4)

// or even a slice of them
cyphers := []*Cypher{cypher1, cypher2, cypher3, cypher4}
cypherC := privateKey.Add(cyphers...)

The original PR: https://github.com/keep-network/paillier/pull/5

Thousand thanks for that one.  Sorry for delay, I forgot about it.
cheers,
didier

authors: didiercrunch pdyraga

repo: didiercrunch/paillier


text:
refactor connections, resolve auto connect

This simplifies the connection api and always enables auto-accept, so should touch some topics in https://github.com/didx-xyz/aries-cloudapi-python/issues/154 and https://github.com/didx-xyz/aries-cloudapi-python/issues/129
Also renames all instances of invite to invitations as part of https://github.com/didx-xyz/aries-cloudapi-python/issues/140

Will look at codacy, forgot that!

repo: didx-xyz/aries-cloudapi-python


text:
🛑 Diego Cornejo's Blog is down

In 7064802, Diego Cornejo's Blog (https://blog.diegocornejo.com) was down:

HTTP code: 500
Response time: 396 ms

Resolved: Diego Cornejo's Blog is back up in 072d2c6.

repo: diegofcornejo/status


text:
support gpt-4

老师您好，请问一下咱们现在这套代码 能支持azure上的gpt4 的模型吗？

我还是按照gpt3.5-turbo的方式部署的，但是貌似不太可以

2023/04/17 07:53:12 proxying request [gpt-3.5-turbo] /v1/chat/completions -> https://bpd.openai.azure.com/openai/deployments/gpt-35-turbo/chat/completions?api-version=2023-03-15-preview
[GIN] 2023/04/17 - 07:53:14 | 404 |  1.720606504s |      172.26.0.1 | POST     "/v1/chat/completions"

部署完之后还是找3.5的这个模型，请教您一下怎么使用 azure的 gpt4 的

@zhangzhaorui 请问您是怎么解决这个的呢？

authors: zdaiot zhangzhaorui

repo: diemus/azure-openai-proxy


text:
Explore enabling large-tables and/or huge-tables by default

I was looking at the compile times for our test suite with various table size features enabled, both when Diesel needed to be compiled, and when only the tests needed to be compiled. This was done on rustc 1.22.0-nightly (325ba23d5 2017-09-19), with incremental comp enabled.
# Baseline
> (cd diesel_tests && touch tests/lib.rs && cargo build --tests --features postgres)
   Compiling diesel v0.16.0 (file:///Users/sean/Documents/Projects/open-source/diesel/diesel)
   Compiling diesel_infer_schema v0.16.0 (file:///Users/sean/Documents/Projects/open-source/diesel/diesel_infer_schema)
   Compiling diesel_tests v0.1.0 (file:///Users/sean/Documents/Projects/open-source/diesel/diesel_tests)
   Compiling diesel_codegen v0.16.0 (file:///Users/sean/Documents/Projects/open-source/diesel/diesel_codegen)
    Finished dev [unoptimized + debuginfo] target(s) in 71.95 secs
>  (cd diesel_tests && touch tests/lib.rs && cargo build --tests --features postgres)
   Compiling diesel_tests v0.1.0 (file:///Users/sean/Documents/Projects/open-source/diesel/diesel_tests)
    Finished dev [unoptimized + debuginfo] target(s) in 24.19 secs

# `large-tables` turned on                                                                                > (cd diesel_tests && touch tests/lib.rs && cargo build --tests --features postgres)
   Compiling diesel v0.16.0 (file:///Users/sean/Documents/Projects/open-source/diesel/diesel)
   Compiling diesel_infer_schema v0.16.0 (file:///Users/sean/Documents/Projects/open-source/diesel/diesel_infer_schema)
   Compiling diesel_tests v0.1.0 (file:///Users/sean/Documents/Projects/open-source/diesel/diesel_tests)
   Compiling diesel_codegen v0.16.0 (file:///Users/sean/Documents/Projects/open-source/diesel/diesel_codegen)
    Finished dev [unoptimized + debuginfo] target(s) in 77.74 secs
> (cd diesel_tests && touch tests/lib.rs && cargo build --tests --features postgres)
   Compiling diesel_tests v0.1.0 (file:///Users/sean/Documents/Projects/open-source/diesel/diesel_tests)
    Finished dev [unoptimized + debuginfo] target(s) in 25.0 secs

# `huge-tables` turned on
> (cd diesel_tests && touch tests/lib.rs && cargo build --tests --features postgres)
   Compiling diesel v0.16.0 (file:///Users/sean/Documents/Projects/open-source/diesel/diesel)
   Compiling diesel_infer_schema v0.16.0 (file:///Users/sean/Documents/Projects/open-source/diesel/diesel_infer_schema)
   Compiling diesel_tests v0.1.0 (file:///Users/sean/Documents/Projects/open-source/diesel/diesel_tests)
   Compiling diesel_codegen v0.16.0 (file:///Users/sean/Documents/Projects/open-source/diesel/diesel_codegen)
    Finished dev [unoptimized + debuginfo] target(s) in 147.86 secs
> (cd diesel_tests && touch tests/lib.rs && cargo build --tests --features postgres)
   Compiling diesel_tests v0.1.0 (file:///Users/sean/Documents/Projects/open-source/diesel/diesel_tests)
    Finished dev [unoptimized + debuginfo] target(s) in 24.12 secs

It looks like these features no longer have any effect on application compilation time, and the large-tables feature might have a small enough effect on the crate's compile time to be worth turning on by default. huge-tables still looks like it doubles our compilation time, but given that most users don't recompile Diesel often, maybe it's worth just enabling that by default, too. I want to explore this more on stable and without incremental comp.

#1520

repo: diesel-rs/diesel


text:
Frontend becomes unresponsive after a while when loading dialogs with embeddable content

Could be related to #1335 ?
cf. https://digdir.slack.com/archives/C07JGSEN02W/p1730818614304199
Experienced with user  26818999827

Jeg opprettet aldri noen egen issue på dette, men jeg opplevde problemet og har forsøkt å gjenskape så godt som mulig det heg holdt på med 5. november. Nå oppleves ikke lenger heng. Test passed.

authors: LeifHelstad seanes

repo: digdir/dialogporten-frontend


text:
Update typo in README.md

I felt this was too mental, why falling back to metrics helps ease of mind when reading this README.

Thanks for this @almereyda!

You're very welcome!
It took longer to write the PR description, than actually forking and fixing it.

authors: UtpalJayNadiger almereyda

repo: diggerhq/digger


text:
Cradle initialization regression

Ghcide has started acting up when initializing the cradle. I can reproduce this loading ghcide itself in VSCode with  a Cabal cradle:
cradle: {cabal: {component: "ghcide"}}

Ghcide is now calling Cabal multiple times where before it did only once. But what is worse, it's doing so in parallel, which leads to file conflicts and eventually to an error.
Full log below.
ghcide version: 0.1.0 (GHC: 8.8.1) (PATH: /home/pepe/scratch/ghcide/dist-newstyle/build/x86_64-linux/ghc-8.8.1/ghcide-0.1.0/x/ghcide/build/ghcide/ghcide) (GIT hash: 00d914efa71de08ae11e4268112817cecdf439e9)
Starting LSP server...
If you are seeing this in a terminal, you probably should have run ghcide WITHOUT the --lsp option!
 Started LSP server in 0.18s
[DEBUG] Set files of interest to: [NormalizedFilePath "/home/pepe/scratch/ghcide/src/Development/IDE/Core/Rules.hs"]
[DEBUG] Starting shakeRun (aborting the previous one took 0.00s)
[INFO] Opened text document: file:///home/pepe/scratch/ghcide/src/Development/IDE/Core/Rules.hs
[DEBUG] Set files of interest to: [NormalizedFilePath "/home/pepe/scratch/ghcide/src/Development/IDE/Core/Rules.hs",NormalizedFilePath "/home/pepe/scratch/ghcide/exe/Main.hs"]
[DEBUG] Finishing shakeRun (took 0.00s, exception: AsyncCancelled)
[DEBUG] Starting shakeRun (aborting the previous one took 0.00s)
[INFO] Opened text document: file:///home/pepe/scratch/ghcide/exe/Main.hs
[DEBUG] Finishing shakeRun (took 0.00s, exception: AsyncCancelled)
[DEBUG] Starting shakeRun (aborting the previous one took 0.00s)
> Resolving dependencies...
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
[DEBUG] Starting shakeRun (aborting the previous one took 0.00s)
[DEBUG] Finishing shakeRun (took 5.39s, exception: AsyncCancelled)
> Resolving dependencies...
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Resolving dependencies...
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Resolving dependencies...
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> ghc-pkg: cannot create: /home/pepe/scratch/ghcide/dist-newstyle/build/x86_64-linux/ghc-8.8.1/ghcide-0.1.0/package.conf.inplace already exists
> cabal: repl failed for ghcide-0.1.0.
>
> Resolving dependencies...
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Resolving dependencies...
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Resolving dependencies...
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Resolving dependencies...
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Resolving dependencies...
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Resolving dependencies...
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Resolving dependencies...
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Resolving dependencies...
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Resolving dependencies...
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Resolving dependencies...
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Resolving dependencies...
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Resolving dependencies...
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Resolving dependencies...
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Resolving dependencies...
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Resolving dependencies...
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> ghc-pkg: cannot create: /home/pepe/scratch/ghcide/dist-newstyle/build/x86_64-linux/ghc-8.8.1/ghcide-0.1.0/package.conf.inplace already exists
> cabal: repl failed for ghcide-0.1.0.
>
[INFO] Hover request at position 298:87 in file: /home/pepe/scratch/ghcide/src/Development/IDE/Core/Rules.hs
[DEBUG] Cancelled request IdInt 3
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
> Resolving dependencies...
> Build profile: -w ghc-8.8.1 -O1
> In order, the following will be built (use -v for more details):
>  - ghcide-0.1.0 (lib) (configuration changed)
> Configuring library for ghcide-0.1.0..
> Preprocessing library for ghcide-0.1.0..
[DEBUG] Finishing shakeRun (took 1m37s, completed)

Bisected to https://github.com/digital-asset/ghcide/pull/408

This seems like a serious regression. Perhaps #408 should be reverted.

I have a fix almost ready

Sorry for the regression and thanks for the fix!

authors: jinwoo mpickering pepeiborra

repo: digital-asset/ghcide