Event/Code change Request on Codeunit 22 - Procedure ApplyItemLedgEntry

We need to extend the functionality of "Prevent negative inventory" to "Transfer orders". To do this we suggest you two ways:

Changue the core directly on Codeunits 22 and 5704:
1.1) Codeunit 5704 TransferOrder-Post Shipment:
On Procedure CheckItemInInventory add the next code:
...
...
WITH Item DO BEGIN
//INIT INSERT
IF PreventNegativeInventory THEN
EXIT;
//END INSERT
GET(TransLine."Item No.");
SETRANGE("Variant Filter",TransLine."Variant Code");
...
...
This code will let the system not showing the advice of negative inventory when posting Transfer
orders only if we have the system configured in that way.

1.2) Codeunit 22 Item Jnl.-Post Line
1.2.1) On Procedure ApplyItemLedgEntry add the next code:
...
...
((Item."Costing Method" = Item."Costing Method"::Specific) AND ItemLedgEntry.Positive) OR
(ItemJnlLine."Direct Transfer" AND (ItemLedgEntry."Location Code" = '') AND
ItemLedgEntry.Positive)
THEN
EXIT;
//INIT INSERT
CLEAR(NoPendingEntries);
//END INSERT
...
...
1.2.2) On Procedure ApplyItemLedgEntry add the next code:
...
...
ELSE
EntryFindMethod := '-';
IF NOT ItemLedgEntry2.FIND(EntryFindMethod) THEN
//INIT INSERT
IF NOT Item.PreventNegativeInventory THEN BEGIN
CASE EntryFindMethod OF
'-': NoPendingEntries := NOT ItemLedgEntry2.FINDFIRST;
'+': NoPendingEntries := NOT ItemLedgEntry2.FINDLAST;
END;
END ELSE
//END INSERT
EXIT;
END ELSE
CASE EntryFindMethod OF
'-':
IF ItemLedgEntry2.NEXT = 0 THEN BEGIN
//INIT INSERT
IF NOT Item.PreventNegativeInventory THEN BEGIN
IF (ItemLedgEntry."Entry Type" = ItemLedgEntry."Entry Type"::Transfer) THEN
ItemLedgEntry2.COPY(OldItemLedgEntry);
NoPendingEntries := TRUE;
END ELSE
//END INSERT
EXIT;
END;
'+':
IF ItemLedgEntry2.NEXT(-1) = 0 THEN
//INIT INSERT
IF NOT Item.PreventNegativeInventory THEN BEGIN
IF (ItemLedgEntry."Entry Type" = ItemLedgEntry."Entry Type"::Transfer) THEN
ItemLedgEntry2.COPY(OldItemLedgEntry);
NoPendingEntries := TRUE;
END ELSE
//END INSERT
EXIT;
END;
OldItemLedgEntry.COPY(ItemLedgEntry2)
...
...
This code will make the system not to exit when no entries are found, but only if we configure
the Item or the system not to prevent negative inventory.
1.2.3) On Procedure ApplyItemLedgEntry add the modifying next code:
...
...
END;
    CheckIsCyclicalLoop(ItemLedgEntry,OldItemLedgEntry,PrevAppliedItemLedgEntry,AppliedQty);
    **//INIT MODIFY
    //IF AppliedQty <> 0 THEN BEGIN
    IF (AppliedQty <> 0) OR ((AppliedQty = 0) AND ((NOT Item.PreventNegativeInventory) AND (NoPendingEntries))) THEN BEGIN
      IF AppliedQty <> 0 THEN BEGIN
    //CONTINUE MODIFY**
        IF NOT OldItemLedgEntry.Positive AND
           (OldItemLedgEntry."Remaining Quantity" = -AppliedQty) AND
           (OldItemLedgEntry."Entry No." = ItemLedgEntry."Applies-to Entry")
  ...
  ...

  ...
  ...
          IF ItemApplnEntry."Cost Application" THEN
            OldItemLedgEntry."Applied Entry to Adjust" := TRUE;
         END;
       **//CONTINUE MODIFY
       END;
       IF ((AppliedQty = 0) AND ((NOT Item.PreventNegativeInventory) AND (NoPendingEntries))) THEN BEGIN
         IF (ItemLedgEntry."Entry Type" = ItemLedgEntry."Entry Type"::Transfer) AND
            (NOT CausedByTransfer)
         THEN BEGIN
           OldItemLedgEntry := ItemLedgEntry;
           InsertTransferEntry(ItemLedgEntry,OldItemLedgEntry,ItemLedgEntry."Remaining Quantity");
           EXIT;
         END ELSE
           EXIT;
       END;
       //END MODIFY**

      OnApplyItemLedgEntryOnBeforeOldItemLedgEntryModify(ItemLedgEntry,OldItemLedgEntry,ItemJnlLine);
      OldItemLedgEntry.MODIFY;
  ...
  ...

  This code will create the entry associated to In transit line of the transfer line, but only if we have configured the system not to prevent negative inventory.

  1.2.4) On Procedure CalcAdjustedCost add the next code:
  ...
  ...
  WITH PosValueEntry DO BEGIN
    SETCURRENTKEY("Item Ledger Entry No.");
    SETRANGE("Item Ledger Entry No.",PosItemLedgEntry."Entry No.");
    **//INIT INSERT
    IF (NoPendingEntries) AND (NOT Item.PreventNegativeInventory) THEN BEGIN
      IF NOT FINDSET THEN
        EXIT;
    END ELSE
    //END INSERT**
    FINDSET;
    REPEAT
      IF "Partial Revaluation" THEN BEGIN
  ...
  ...

  This code will let the system not to crash when the entry is not found when calculating adjusted cost, but only if we have configured the system not to prevent negative inventory.

  1.2.5) On Globar vars add:
  Name		DataType	Subtype	Length
  NoPendingEntries	Boolean

Add events in Codeunits 22
2.1) Codeunit 22 Item Jnl.-Post Line
2.1.1) On Procedure ApplyItemLedgEntry add the next code:
...
...
ELSE
EntryFindMethod := '-';
IF NOT ItemLedgEntry2.FIND(EntryFindMethod) THEN
//INIT INSERT
OnBeforeInsertFirstApplication(ItemLedgEntry2,ItemLedgEntry,ItemTrackingCode,NoPendingEntries,Handled);
if not Handled then
//END INSERT
EXIT;
END ELSE
//INIT INSERT
OnBeforeInsertNotFirstApplication(ItemLedgEntry2,ItemLedgEntry,ItemTrackingCode,NoPendingEntries,Handled);
if not Handled then
//END INSERT
CASE EntryFindMethod OF
...
...
2.1.2) On Procedure ApplyItemLedgEntry add the modifying next code:
...
...
CheckIsCyclicalLoop(ItemLedgEntry,OldItemLedgEntry,PrevAppliedItemLedgEntry,AppliedQty);
//INIT INSERT
OnBeforeManageAppliedQty(AppliedQty,NoPendingEntries,ItemLedgEntry,CausedByTransfer,OldItemLedgEntry,Handled);
If Handled then
exit
else
//END INSERT
IF AppliedQty <> 0 THEN BEGIN
...
...
2.1.3) On Procedure CalcAdjustedCost add the next code:
//INIT INSERT
OnBeforeCalcAdjustedCost(PosItemLedgEntry,AppliedQty,AdjustedCostLCY,AdjustedCostACY,DiscountAmount)
IF IsHandled THEN
EXIT;
//END INSERT
AdjustedCostLCY := 0;
AdjustedCostACY := 0;
DiscountAmount := 0;
...
...
2.1.4) On Procedure CalcAdjustedCost add the next var:
Name		DataType	Subtype	Length
IsHandled	Boolean
2.1.5) On Globar vars add:
Name		DataType	Subtype	Length
NoPendingEntries	Boolean
2.1.6) Add public events:
LOCAL [IntegrationEvent] OnBeforeInsertFirstApplication(VAR ItemLedgEntry2 : Record "Item Ledger Entry";VAR ItemLedgEntry : Record "Item Ledger Entry";VAR ItemTrackingCode : Record "Item Tracking Code";VAR NoPendingEntries : Boolean;VAR IsHandled : Boolean)
LOCAL [IntegrationEvent] OnBeforeInsertNotFirstApplication(VAR ItemLedgEntry2 : Record "Item Ledger Entry";VAR ItemLedgEntry : Record "Item Ledger Entry";VAR ItemTrackingCode : Record "Item Tracking Code";VAR NoPendingEntries : Boolean;VAR IsHandled : Boolean)
LOCAL [IntegrationEvent] OnBeforeManageAppliedQty(VAR AppliedQty : Decimal;VAR NoPendingEntries : Boolean;VAR ItemLedgEntry : Record "Item Ledger Entry";VAR CausedByTransfer : Boolean;VAR OldItemLedgEntry : Record "Item Ledger Entry";VAR IsHandled : Boolean)
LOCAL [IntegrationEvent] OnBeforeCalcAdjustedCost(VAR PosItemLedgEntry : Record "Item Ledger Entry";VAR AppliedQty : Decimal;VAR AdjustedCostLCY : Decimal;VAR AdjustedCostACY : Decimal;VAR DiscountAmount : Decimal)

Sorry, I have noticed you have marked this issue as "extensibility-enchancement". I agree the option 1) should by marked like this, but let me remind you that the opcion 2) is an Event request.
Thank you

Sorry, when we were applying the code we noticed two mistakes in option 1) and section 1.2.2). So this section should be like this:
1.2.2) On Procedure ApplyItemLedgEntry add the next code:
...
...

This code will make the system not to exit when no entries are found, but only if we configure
the Item or the system not to prevent negative inventory.
Sorry about that
Regards

Sorry, we cannot implement any of suggestions above. We need to understand your scenario to suggest feasible solution. Can you describe it, specifically why you want to do it on item application level?

I suppose you are refering to the code changin in Condeunit 22 ApplyItemLedgerEntry.
The code suggested will make the system not to exit when no entries are found, but only if we configure
the Item or the system not to prevent negative inventory. If the system does not exist from than function, with the event suggested in point 2, we well be able to apply the "Prevent negative inventory" when a transfer order is posted.

I suppose you are refering to the code changin in Condeunit 22 ApplyItemLedgerEntry.
The code suggested will make the system not to exit when no entries are found, but only if we configure
the Item or the system not to prevent negative inventory. If the system does not exist from than function, with the event suggested in point 2, we well be able to apply the "Prevent negative inventory" when a transfer order is posted.

@bgonzalez-ib - do you want to allow negative inventory for transfer order?

@bgonzalez-ib - do you want to allow negative inventory for transfer order?

Yes, but only if we have the system configured in that way, that is the modification and it is installed on the client database since June with no problems.

Yes, but only if we have the system configured in that way, that is the modification and it is installed on the client database since June with no problems.

We are not very enthusiastic about enabling such tricks without very good purpose. There is a significant risk that it will affect inventory costing.
Could you please describe the scenario, why do you need to transfer goods before receiving them?
Maybe we can find another solution?

We are not very enthusiastic about enabling such tricks without very good purpose. There is a significant risk that it will affect inventory costing.
Could you please describe the scenario, why do you need to transfer goods before receiving them?
Maybe we can find another solution?

First of all sorry for delaying on answering.
Our client has two external programs where they manage product manufacturing. These fabrications cannot be integrated online in Business Central due to limitations in these external programs and they are carried out after (the next day). The outputs (sales and transfers) of these productions are only managed in Business Central, so the customer needs to output a finished product whose input will not be produced until the next day. In sales there is no problem since making the configuration to allow negative stocks is enough but in Transfers this configuration is not possible and there must be positive stocks of the product to be able to make the shipment.

@bgonzalez-ib
You have described a feature, and even if it works fine for one customer, it is not enough for us to simply put it in the code. There must be scenarios confirmed by automated tests.
For the new features please submit a product suggestion on https://aka.ms/bcideas
Do the events of the option 2 make sense without implemented option 1?


🔄 Synced file(s) with jhudsl/DaSL_Course_Template_Bookdown

Synced local file(s) with jhudsl/DaSL_Course_Template_Bookdown.

Changed files

Synced local  .github/workflows/render-bookdown.yml with remote  .github/workflows/render-bookdown.ymlSynced local  .github/workflows/render-preview.yml with remote  .github/workflows/render-preview.ymlCreated local  .github/workflows/docker-build-test.yml  from remote  .github/workflows/docker-build-test.ymlSynced local  code_of_conduct.md with remote  code_of_conduct.md

This PR was created automatically by the repo-file-sync-action workflow run #1417888960

Please carefully review these changes and decide which are useful for your course.
See the release notes: https://github.com/jhudsl/DaSL_Course_Template_Bookdown/releases

If you don't want the changes from a particular file, you can always revert that particular commit before merging the sync PR.
If you will not want any updates on this file in the future, you may want to remove a file from being synced in your repo by reconfiguring the sync file.

If you want only some changes, but they are not on a whole file basis, you could check out the branch and make manual edits. To checkout the branch, navigate to your own repository you should be able to run:

git checkout repo-sync/DaSL_Course_Template_Bookdown/default

If you don't want any of the changes you can close the PR entirely.

You may want to unenroll your repository from the sync GitHub actions by filing a PR on DaSL_Course_Template_Bookdown
to delete your repo name from this file if this will continue to be the case.


The pre-trained model you are loading is a cased model but you have not set do_lower_case to False.

I initialized the tokenizer and the model like
def load_bert_score_model(bert="bert-base-multilingual-cased", num_layers=8):

    assert bert in bert_types

    tokenizer = BertTokenizer.from_pretrained(bert, do_lower_case=True)
    model = BertModel.from_pretrained(bert)
    model.eval()
    device = 'cuda' if torch.cuda.is_available() else 'cpu'
    model.to(device)

    # drop unused layers
    model.encoder.layer = torch.nn.ModuleList([layer for layer in model.encoder.layer[:num_layers]])

    return model, tokenizer

so setting the do_lower_case=True, but I'm getting this warning:
The pre-trained model you are loading is a cased model but you have not set `do_lower_case` to False. We are setting `do_lower_case=False` for you but you may want to check this behavior.

Hi! You seem to be loading a cased model (such as the bert-base-multilingual-cased), but you're specifying do_lower_case to your tokenizer, which strips accents and lowercases every character.
The model you specified has been trained with uppercase and lowercase characters as well as accent markers, so you should use it with such characters as well. If you're looking at using only lowercase characters, it would be better for you to use an uncased model (such as the bert-base-multilingual-uncased).

@LysandreJik that is correct, thank you.


Gem trader

This is less of a bug but more of a quality of life feature request. You added custom items to the Gem Trader like spirit cubes and artifacts, but the gems were removed. Can you have the Gem trader sell the new items you added plus the gems it used to sell?

It was a design choice to remove the gems, but I can add them back for you. 👍 It will be there in the release of next week.

do you have a discord server? Or is there a common server where you hang out. It would be fun to talk to you.

id hate to open this back up, but I don't see gems still. Unsure if it was fixed or not, trying to build a version where gem traders aren't touched but normal shop vendors are, but it keeps failing


Revert "[gulp] using typescript to maintain the gulpfile"

Reverts buzinas/tslint-eslint-rules#112

Did something happen with the modification using typescript for the gulpfile?

The build time increased by almost one minute, and also I didn't like the on-the-fly transpilation using eval, nor the class and decorators for the gulp-task.
I'm taking some of the work you did in the other PR and I'll be merging it in a few minutes.

Sounds good. Yeah, we should get the bug fixes at least. Too bad things got slower :(.

Would it make any difference if we use ts-node? This way we won't need to have gulpfile.js at all. We could skip the gulpclass stuff and just write the gulp file but using typescript. I'll try again in another branch. How did you measure the build time? I assume it wasn't this:
$ gulp build
[22:29:26] Using gulpfile ~/Github/tslint-eslint-rules/gulpfile.js
[22:29:26] Starting 'lint'...
[22:29:28] Finished 'lint' after 2.61 s
[22:29:28] Starting 'build'...
[22:29:30] Finished 'build' after 2 s

In fact, I was talking about the *CI time.
About the gulpfile, I think I'm happy with it in Javascript. If at least TypeScript had something similar to the babel-register, we could probably use it.

I see. darn, in that case then ts-node probably won't make a difference. Perhaps at a later time. Let me know if you need some help incorporating the changes to fix the async problems.

@jmlopez-rod I tried to incorporate the changes, please feel free to fix them if I forgot anything.


Move ES module build to es/

This makes us consistent with Redux

Let's make a note of this in the Changelog so that those living on the edge and building via these files know to update.

isn't moving the directory of something a breaking change?

oh, nvm, main solves it.

jsnext:main, but yeah – the idea is that users should be importing this as 'react-router' anyway, not reaching into es/ manually.


Expose utilities to avoid UI flickers when asynchronous providers update

A few things:

https://github.com/rrousselGit/riverpod/issues/1773

Due to https://github.com/rrousselGit/riverpod/issues/1774 providers need a way to optionally synchronously await a value
Maybe we could have FutureOr<T> value = ref.watch(futureProvider.futureOr
Or maybe we could have an alternative using SynchrounousFuture

Because async functions always resolve asynchronously, this forces a one-frame delay before a value is emitted.
A workaround is to do:
final provider = FutureProvider<Model>((ref) async {
  ref.state = AsyncData(Model());
  return ref.state;
});

but that's a bit tedious to be broadly used.
Maybe we could have:
final provider = FutureProvider<Model>((ref) async {
  return ref.setState(Model();
});

where setState is T setState(T value) { state = AsyncData(value); return value;}

This was done previously with when(skipLoadingOnRefresh/Reload: bool) flags


Camel CDI default context is shared across EAR sub deployments

As per issue title, the default context created by the CDI extension ends up being shared across all sub-deployments within an EAR:
This has some odd side effects....
Doing the following in each each sub-deployment application always results in the same Camel Context being injected
public class Foo {
  @Inject
  CamelContext camelContext
}

Similarly if I create RouteBuilder classes in every sub-deployment, they each get added to the default context.
Not sure if that's the correct behaviour for an EAR or not. It could end up being quite confusing. @astefanutti any thoughts on this?
I know there are ways of working around this via @ContextName or with custom producer methods, but the default behaviour is problematic because it becomes impossible to wire the CamelContext to an appropriate ClassLoader.

It seems there is a single / global BeanManager instance for the EAR, which is provided to Camel CDI and other CDI archives, so any beans and injection points get globally resolved. There is a nice article about CDI in EAR that tends to confirm how WildFly behaves: https://struberg.wordpress.com/2015/02/18/cdi-in-ears/.
From the logical, programming model, standpoint, what would users expect / want? A default Camel context per WAR? Do people that structure their application into multiple WARs want to achieve isolation or modularity? For the former, it would imply having a Camel CDI extension per sub-deployment. For the later, that would be a single Camel CDI extension instance for the entire EAR.
As opposed to class loading, there is no way to work-around bean managers structure inside a CDI extension. So, if we want to achieve isolation, the only option I see would be to deploy a Camel CDI extension instance per sub-deployment.

Thanks for that response.
Turns out loading the extension per sub-deployment is not possible. WildFly ensures that only one extension instance is ever loaded:
https://github.com/wildfly/wildfly/blob/master/weld/common/src/main/java/org/jboss/as/weld/deployment/WeldPortableExtensions.java#L17-L26
Regardless of whether custom CDI extensions are on the class path, EAR deployments will still only ever have a single BeanManager instance. So the default CamelContext being shared across all sub-deployments seems to be the correct (for WildFly) behaviour.
I'll close this issue. But in general, it's still confusing to me why it seems valid for a CDI bean, based on a class from one WAR sub-deployment, can be injected into a bean from a different WAR sub-deployment. By default the WAR class loaders within an EAR are isolated, so inevitably such a scenario results in an NCDFE. Although there are ways around this via manifest Class-Path entries.

I'll close this issue. But in general, it's still confusing to me why it seems valid for a CDI bean, based on a class from one WAR sub-deployment, can be injected into a bean from a different WAR sub-deployment. By default the WAR class loaders within an EAR are isolated, so inevitably such a scenario results in an NCDFE. Although there are ways around this via manifest Class-Path entries.

I agree. In our use case, that is from a CDI extension standpoint, it's a bit different as the Camel CDI extension uses the Camel classes and discover beans of these types.


feat!: inlined schema definitions inside the KafkaSchema custom resource

v1beta1 approach was based on the convention that the actual schema (payload/structure) was stored in configmap and only referenced by KafkaSchema resource. There are a few problems related to that approach:

inconsistent behaviour - when you create a schema resource, configmap needs to be already applied in your namespace. but finalizer deletes that configmap during cleanup
race condition between K8S resources - during reconciliation, it's assumed that configmap was updated prior to updating KafkaSchema. If it wasn't, changes will not be applied. On the other hand, configmap has to be deleted after the custom resource, otherwise finalizer will fail.
difficulties in managing "independent" K8S resources in a single chart - it's not easy/recommended to use owner references from within a single chart, and playing with finalizers to "block deletion" of configmap is tricky

Instead, I would like to propose a simpler approach, where the entire KafkaSchema resource is self-contained. You can define your schema payload directly in the resource or use helm templating to populate it from an external file
BREAKING CHANGE: CR no longer supports reference to schema configmap through spec.data.configRef

halo, greate work!

I've been waiting for this - thank you!

Inline definitions are ok, but plaintext credentials for schema registry in CR don't make me happy 😄

@Brightside56 agreed. I'll fix that in another PR. Please don't use it for the time being ;)

@Brightside56 that is just a comment or you need to use credentials in your use case? because we wanted to drop authentication feature for now, as there is a plan to do it in more sophisticated way to allow different auth methods, not only Basic

@slomkarafa Yes, I need to use credentials and I need them to be processed securely

@Brightside56 agreed. I'll fix that in another PR. Please don't use it for the time being ;)

For now it's more than ok. I'm concerned more with issues like absence of schema validation and possibility to check resources health using CR status

@Brightside56 and possibility to check resources health using CR status that's already planned, but we (or mainly @Tomek-Adamczewski :p) are doing that in the meantime, so we strongly encourage to contribution :p

@Brightside56 on schema validation - schema registry should do that for you. do you think we should duplicate that responsibility in operator?
Anyway, I've enabled issues in this repo for you to start throwing darts at me. When I think what this operator should actually do, I'm considering creating a completely new api group and start from scratch, as I won't be able to maintain any compatibility.


Partially fix setRenderToTexture()

The image is flipped vertically and the depth+stencil buffers don't work, but at least you can work around the former. The important thing is that rendering to texture works at all.
Another note: setRenderToBackBuffer() will leave the depth and stencil buffers disabled (suggesting that the answer to line 183 is "no"). You'll have to call GL.enable(GL.DEPTH_TEST) and/or GL.enable(GL.STENCIL_TEST) to re-enable them.

I removed those GL.disable calls in my fork since I didn't think they were needed. I encountered issues with scissor when I used render target texture, because scissor had been disabled by setRenderToBackBuffer().

This PR is outdated, and my new PR will fixes issues with render target textures.
https://github.com/openfl/openfl/pull/1237
GL.BGRA_EXT is not a valid format in OpenGL ES 2.0 either, but almost all devices support that format via extension.
https://www.khronos.org/registry/gles/extensions/EXT/EXT_texture_format_BGRA8888.txt

I meant BGRA is not part of OpenGL ES "standard". It's support is just not mandatory.


Fixed dangling promise during abort

The problem is probably due to IntermittentIterator not awaiting the last remaining promise.

Just forgot that .then() creates a new promise.


To fix format

Description
From #53, a bug was found when changing the default value of format, vix. yyyy/mm/dd to value like dd/mm/yyyy will render the date go haywire.
Step to reproduce
Live demo

Side note: it would be nice to just get Date values out of the component. At the moment I need to "manually" parse the date string and convert to Date. It's also unclear to me if or how the component supports the ISO format for dates, which would make it easy to convert it back to a Date value.

Fixed in v2.9.0


[BUG] Eww isn't hot reloading with symlinked configs

Checklist before submitting an issue

[X] I have searched through the existing closed and open issues for eww and made sure this is not a duplicate
[X] I have specifically verified that this bug is not a common user error
[X] I am providing as much relevant information as I am able to in this bug report (Minimal config to reproduce the issue for example, if applicable)

Description of the bug
Eww doesn't hot reload when using symlinks for the config. I'm using https://github.com/SuperCuber/dotter so it auto creates these symlinks.
Reproducing the issue

Create a symlink to eww configs
Edit the config
Eww doesn't hot reload

Expected behaviour
It hot reloads
Additional context
No response

I'm unable to reproduce that issue, for me hot-reloading configs with symlinks does work as expected -- do you experience the same issue with non-symlinked config? Or if you open eww by referring to the symlink target rather than the symlink?

A non-symlinked config works properly and referring eww to the symlink target also works properly. It used to work properly but it broke a couple days into having eww.

It's because of symlinking the files and not the directory. I've changed it now since notify doesn't support it (https://github.com/notify-rs/notify/issues/381) to a directory symlink. It would be better to not have to do this though since some other stuff (from my scripts) is generated to the config directory.


Update AutobahnTestServer to use IISIntegration

@Tratcher I am updating the autobahn server to use IISIntegration since it was needed as a test sample for IIS on nano. Since I don't see any downsides to having this change in our repo, I was thinking we can just take them for the dev branch. This is currently on release since that's what needs to be tested but I'll make a separate change in dev if you agree this is useful.

:shipit: in dev.

merged in dev in https://github.com/aspnet/WebSockets/commit/37931a9fa56d558ab08130783a776fd9fc7a42ee. Will leave this branch for testing though.


Spanish and French translations

Not entirely confident on using suave and doux instead of de peluche and pelucheux, but decided to go with the former for consistency with the majority of existing translations

sure :+1:


Watch channel queue dictionary changes size during iteration

Sentry Issue: BOT-84
I suppose it just needs to create another copy for iteration. Is there a more elegant solution?
RuntimeError: dictionary changed size during iteration
  File "bot/cogs/watchchannels/watchchannel.py", line 183, in consume_messages
    for user_channel_queues in self.consumption_queue.values():

The message queue consume task has failed with:

This could be fixed by either making a copy of the dict, or more preferably, by not popping from it when removing the user. However, #999 will still cause issues.


Can the new version be published to npm?

Hey @csquared, thanks for doing MR #13 -- can you also publish the update to NPM?  I think the package.json is already bumped, so just publishing should be sufficient.
Thanks, and thanks for the node implementation of this. =)

Just published!
Thanks and glad it's working for you :)

On Sep 28, 2017, at 6:59 AM, EyePulp<EMAIL_ADDRESS>wrote:
Hey @csquared, thanks for doing MR #13 -- can you also publish the update to NPM? I think the package.json is already bumped, so just publishing should be sufficient.
Thanks, and thanks for the node implementation of this. =)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Awesome, thanks so much!

andrew -

On September 28, 2017 at 12:42:59 PM, Chris Continanza (
<EMAIL_ADDRESS>wrote:
Just published!
Thanks and glad it's working for you :)

On Sep 28, 2017, at 6:59 AM, EyePulp<EMAIL_ADDRESS>wrote:
Hey @csquared, thanks for doing MR #13 -- can you also publish the update
to NPM? I think the package.json is already bumped, so just publishing
should be sufficient.
Thanks, and thanks for the node implementation of this. =)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/csquared/fernet.js/issues/15#issuecomment-332911252,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOGqeqvfnn9s7gOR82VKHxEcRp6Z407ks5sm9qZgaJpZM4PnUA4
.


PEP8 and Google-style docstrings

Use pylint and make an effort to comply with PEP8 style recommendations. Strict compliance is not mandatory but there is ample opportunity for improvement, particularly with respect to docstrings.
Use Google-style comments for classes and functions. See https://google.github.io/styleguide/pyguide.html#Comments and mounts.py for an example.

Significant lint removal was performed in bbaba30b. Expect another update in 2026.

This is essentially complete. There are just a couple of minor issues that pylint complains about.


[Bug]: Cards are not working properly under the disease section

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug

When the cursor is pointed at the card it should turn and when it is removed it should come to its original state but it is not coming to its original state.
The card should have a button called read more as only half of the text is visible.
The card should have its own heading at the back. If it is about apple then it should have apple as heading as it is difficult for user to turn it over again and again to see what is he reading.

Expected behavior

The card should return to its original state when cursor is removed
Read more button should be added
Should have a heading regarding what it is describing

Add ScreenShots
https://github.com/user-attachments/assets/29ffd761-47b7-4942-af65-b564cead9875
On which device are you experiencing this bug?
Chrome, Windows
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

Hey @manikumarreddyu , Can i know y are the issues closed?

when it comes to follow us icons ..they are tilting..it is not a bug ..it is feature..
you can work on this.. @sriraghavi22

@manikumarreddyu , I am Mentor Assigned for the project. Can you please give rights to review the codes or maintainer rights.

hi @sriraghavi22 can you please let me know..how much time do you need to fix this issue..?

https://agro-tech-ai.vercel.app/
hi @sriraghavi22 can you please stop working on it....because we updated it..

https://www.linkedin.com/in/manikumarreddyu connect me here..if you have any doubts


Windows 11 compatibility for makeprofile.ps1 script

Please add a note to advise that the powershell script to deploy the VPN profile fails by default on Windows 11.
This is during the part where it tries to remove existing instances of the profile.
I had to comment out the EXIT code on the try/catch block to allow the script to deploy the profile.
Searching online, it seems this is because of a bug in Windows 11 that remains to be fixed.
Thanks

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

ID: 77e14da1-102d-3ddf-e2a1-a20ce533b95a
Version Independent ID: 374edc4c-f527-b7b7-c291-353928b97d8d
Content: Configure Windows 10 Client Always On VPN Connections
Content Source: WindowsServerDocs/remote/remote-access/vpn/always-on-vpn/deploy/vpn-deploy-client-vpn-connections.md
Product: windows-server
Technology: remote
GitHub Login: @Teresa-Motiv
Microsoft Alias: v-tea

From https://github.com/MicrosoftDocs/windowsserverdocs/issues/6823
Seems there is another issue reporting the same here:
In the MakeProfile.ps1 script, where it tries to enumerate and delete old VPNs via this:
$InstanceId = $deleteInstance.InstanceID
That doesn't work in Windows 11 - "A general error occurred that is not covered by a more specific error code"... which appears to be a WMI/CIM bug with the class.
It would seem sensible for MS to review and update the script to make it Windows 11 friendly?

#please-close Fixed in: https://github.com/MicrosoftDocs/windowsserverdocs-pr/pull/3398


Allow for NFC normalization in output

I can easily write a wrapper to have NFC normalization in output, as this is useful for my purposes, and LingPy uses NFC, but I suggest it would not be difficult to already include this in the tokenizer itself, that is, when initializing the instance, one could just pass a keyword specifying normalization, or one could allow for a keyword in the output of t.transform. Or would you prefer me to handle it from my side?

See https://github.com/bambooforest/segments/blob/fdb6b7ef98b8e013139c61334d6b53f6aa0920a7/segments/tokenizer.py#L161

cool, thanks a lot!

Looks like this will be:
NFC, NFKC, NFD, and NFKD
as per Python unicodedata

Yeah, that should probably checked, i.e.:
assert form is None or form in ['NFC', 'NFKC', ...]

ok, i'll write a test


[ESP32] Support Thread and Wi-Fi network revert configuration

Problem
Platform ESP32 do not support Wi-Fi reverting network nor Thread reverting network to disconnect state.
Change overview

Removed check for KVS value point to support Thread reverting network to disconnect state
Added RevertConfiguration for Wi-Fi

Testing
RevertConfiguration for Wi-Fi and Thread network on ESP32-C6.

@chshu @dhrishi PTAL.


Why is the css/scss reliant on classes?

Overview
I am using carbon-components for a project. I find the CSS really over-verbose and unweildly. Let's look at this example of a transactional modal:

Label (Optional)

Modal Title

      <button class="bx--modal-close" type="button" data-modal-close>
        <svg class="bx--modal-close__icon">
          <use xlink:href="/carbon-icons/bluemix-icons.svg#icon--close"></use>
        </svg>
      </button>

Modal text description

      <button class="bx--btn bx--btn--secondary" type="button" data-modal-close>Cancel</button>
      <button class="bx--btn bx--btn--primary" type="button" data-modal-primary-focus>Save</button>

There is a class for almost every element, when an element can easily be inferred by the structure. For example, instead of have three nested classes: bx--modal > bx--modal--container > bx--modal-header, there could be the one class on the top level element, and use .bx--modal > div to select the modal-container and a  element selected by .bx--modal header. An overly verbose css class system is very unnecessary and clutters the HTML making it difficult to read.
The button is another example of over-verbose and redundant information:
<button class="bx--btn bx--btn--primary" type="button" disabled>Primary button</button>
We know it is a button element, so why do we need a bx-btn class? Perhaps if we want to make our button bluemix-ey just make a bx class for the button. And look, we have another class with btn in it... bx--btn--primary! This makes it very difficult for a developer to remember, and to see clearly what is happening in a big html template. The above can be easily achievable like so:
<button class="bx primary" type="button" disabled>Primary button</button>
using these CSS selectors: button.bx, button.bx.primary.
I know all of this style is throughout the whole application. But I think there is a lot of mileage on utilising CSS more effectively by removing the amount of classes needed to implement the components, and rely more on structure and selectors that can work on multiple classes.
Feature: cleaner HTML needed
  As a developer
  I want fewer CSS classes to use in HTML
  So that I can developer faster, and have more maintainable code

I think a big change like this would need a major version change too, it would break projects already using this system.

Hey Andrew! Let me go through your points and why we built the system the way we did. The tl;dr is that we built the system with our priority on being flexible, consistent, and descriptive at the cost of verboseness, and that's not going to change. We've found that users can glance at the markup or the css and have a clear idea what each piece is doing.
1. Why bx-- on everything
Namespacing essentially allows applications to consume Carbon in pieces - which is, as it were, the primary way applications are being converted. We in fact have done a lot of work to ensure that Carbon is flexible enough to be consumed it pieces - the global reset can be turned off with a scss variable and injected into each class that requires it, for example. Most of the users for the last year or so already had applications and were shifting over to the system.
2. Why bx--btn bx--btn-primary classes
This architecture is called Block Element Modifier. While verbose, it clearly spells out the relationship between the elements. That way when a developer wants to use a secondary button, or perhaps wants to skin the button a certain way, it's always consistent. We also make sure not to clobber the global button - again, this is to let applications integrate smoothly.
**3. Why not just do .bx-modal > div
There's a couple problems with this style of css. The first is that it's not descriptive of what it's actually doing. While I'll probably use this style of css on my personal projects, working in larger applications with multiple members this becomes more and more untenable.
The other problem with using something like .bx-modal > div is that we don't know what other elements users are going to put in there (maybe an artifact of a framework they're using, maybe a modification for their use case).
Hope that explains why we architected our system this way


Show Editor freezing QLC+ for several seconds when first track is infinite

Hi there.
Describe the bug
I can confirm a bug report from the forums: https://forum.qlcplus.org/viewtopic.php?p=64701
Every switch to and from the Shows tab completely freezes QLC+ 4.13.0 for several seconds when hold of the first track is set to infinite and a second track exists within this show.
To Reproduce
Steps to reproduce the behavior:
In a new QLC+ session. No fixture needed.

Create two (empty) Scenes.
Create a Show in the Shows tab.
Add the first Scene to the Show at the very beginning. Set Hold to infinite.
Add the second Scene to the Show.
Switch to e.g. Functions tab.

Now the damage is done. One CPU core maximizes to 100% and QLC+ hangs for several seconds. And each time one switches to or from the Shows tab happens the same.
This does however not happen when the hold duration of the first scene is not infinite but incredibly high.
Expected behavior
No freezing.
Desktop (please complete the following information):

OS: Linux Mint
QLC+ Version 4.13.0 GIT
Two different laptops with Intel CPU.

Additional context
Debug Level 0 output:
Universe thread started 0
Universe thread started 1
Universe thread started 2
Universe thread started 3
SimpleDeskEngine::SimpleDeskEngine(Doc*)
void SimpleDesk::slotUniversePageChanged(int)
CueStack* SimpleDeskEngine::createCueStack()
[InputOutputPatchEditor] Fill tree for universe:  0
virtual void ShowManager::showEvent(QShowEvent*)
virtual void ShowManager::hideEvent(QHideEvent*)
virtual void FunctionManager::showEvent(QShowEvent*)
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
SceneEditor::SceneEditor(QWidget*, Scene*, Doc*, bool)
SceneEditor::SceneEditor(QWidget*, Scene*, Doc*, bool)
virtual SceneEditor::~SceneEditor()
virtual void FunctionManager::hideEvent(QHideEvent*)
void SceneEditor::slotFunctionManagerActive(bool)
virtual void ShowManager::showEvent(QShowEvent*)
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[ShowManager] updateMultiTrackView...
QXcbConnection: XCB error: 3 (BadWindow), sequence: 1010, resource id: 19459778, major code: 40 (TranslateCoords), minor code: 0
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
Start time:<PHONE_NUMBER> Duration: 0
virtual void ShowItem::mouseReleaseEvent(QGraphicsSceneMouseEvent*) mouse RELEASE event - < 120 > - < 49 >
void MultiTrackView::slotItemMoved(QGraphicsSceneMouseEvent*, ShowItem*) event - < 120 > - < 49 >
SceneEditor::SceneEditor(QWidget*, Scene*, Doc*, bool)
Idx:  0 , steps:  1
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
[FunctionsTreeWidget] TREE item changed
Start time:<PHONE_NUMBER> Duration: 0
virtual void ShowManager::hideEvent(QHideEvent*)
void SceneEditor::slotFunctionManagerActive(bool)
Function stop(). Name: "New Sequence 3" ID:  3 source:<PHONE_NUMBER> 0
virtual SceneEditor::~SceneEditor()

Thanks!


Caching not reliable on MSVC with additional flags

The commandline passed to ccache seems to be interpreted the wrong way as ccache is not handling MSVC specific options the correct way. Might need to stop hardcoding the CCACHE_COMPILERTYPE=clang and possibly also use clang-cl on some platforms.
In addition it would be great to provide flexibility for overriding this from the outside.

Fix included in a4c451ceac414f8acf7d76985f03d64e6caf2142 released as v0.2.4


tests: sync_after_each_test -> sync_between_tests

Problem
We are seeing frequent pageserver startup timelines while it calls syncfs().  There is an existing fixture that syncs after tests, but not before the first one.  We hypothesize that some failures are happening on the first test in a job.
Summary of changes

extend the existing sync_after_each_test to be a sync between all tests, including sync'ing before running the first test.  That should remove any ambiguity about whether the sync is happening on the correct node.

This is an alternative to https://github.com/neondatabase/neon/pull/8957 -- I didn't realize until I saw Alexander's comment on that PR that we have an existing hook that syncs filesystems and can be extended.
Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

This made it through two benchmark runs without failures, so cautiously optimistic that it at least does no harm


Nullable flag is ignored for root type definitions

The nullable flag is ignored in case it is in a root type definition and used as reference, e.g. the property firstName in the Person schema is not considered as nullable:
Person:
  type: object
  properties:
    firstName:
      $ref: '#/components/schemas/FirstName'

FirstName:
  type: string
  description: first name
  nullable: true

This is also the case for root object and array types.

This is also the case for root object and array types.


Uint32 properties

Uint32 properties seem to no longer be supported as data types. They worked in v2. Can they be added back in?

Bson specs has no support for Uin32, but in BsonMapper, Uint32 are converted into Int64 here:  https://github.com/mbdavid/LiteDB/blob/master/LiteDB/Mapper/BsonMapper.Serialize.cs#L72

Okay then I guess the only issue is the implicit operators in BsonValue don't have Uint32 support?


Confused about importing typescript types

Please bear with me as I'm a newbie to both ReasonML and genType. I'm confused because it seems to me that the readme implies I should be able to consume typescript types with something like
<EMAIL_ADDRESS>"./MyMath"]
type complexNumber;

but either I'm doing something wrong, it doesn't work, or I'm misunderstanding what it should actually do. Should it automatically generate a type definition that I can use in Reason to allocate new objects etc.? The examples all seem to define the types in reason when importing, which works, but I don't understand how is it different to using Bucklescript's interop directly.
Should this work?
//  Bla.ts
export type MyType = {
	readonly n: string;
}

// Test.re
<EMAIL_ADDRESS>("./Bla", "MyType")]
type myType;

let test : myType = {
	n: "test"
};

Here I get the error "Unbound record field n".
Or do I need to do this?
<EMAIL_ADDRESS>("./Bla", "MyType")]
type myType = {
	n: string
};

Exporting on the other hand works and is intuitive. Ultimately what I'm most interested in is consuming js/ts libraries with typings in reasonml and maybe my own typescript code. Should I look elsewhere? I know there's ReasonablyTyped, but it doesn't seem to be currently maintained.
Anyway thanks for making this library. Even if it's just for the exporting reason code to typescript, it makes me more confident investing my time in reasonml.

@cician your understanding seems correct.
As far as types are concerned, Reason is always the source of truth, and there's no automatic conversion from e.g. TypeScript. A type defined on the TypeScript side is only imported as abstract, meaning on the Reason side you don't know how it's defined.
Instead, if the type is defined on the Reason side, its corresponding type can be used also when importing a TypeScript value. The difference w.r.t. using bucklescript's interop directly is that your types get checked (specifically, in case of inconsistency, a type error should be caught by TypeScript).
As far as the other direction, converting types automatically from TypeScript, there have been a number of lines of work, one of which is ReasonablyTyped. The observation seems to be that this works on simple cases, but it's not so clear how the conversion should work on arbitrary TS types.

Cristiano was faster, but i decided to post my comment too :D
Hi @cician
I am just a genType user - so some things in my answer may not be 100% correct.
genType generates types from Reasonml code to use and typecheck on the other side (JS/Flow/TS). It will never understand external types in Reasonml world (at least now, no idea about future plans), but offers possibility for TypeScript to check genType output.
In your code
<EMAIL_ADDRESS>("./Bla", "MyType")]
type myType;

Creates abstract type, which genType will "link" in generated files to real Bla.MyType.
To use it in Reasonml code you have two options:

also use some external function that will return myType (probably some TS function)
type it in Reasonml again, but let TS to verify genType output based on usage/bindings

[@gentype]
type myType = {
 .
 "n": string
};

You can read here about abstract type

Thank you for a prompt responses.
I'm more talking to myself here as I'm facing a technology choice for my project. So reassuming:
GenType as it stands does not provide a fuctionality like ReasonablyTyped or ts2fable to automatically generate ReasonML types from TypeScript definitions. No one so far managed to automagically and consistently convert lousier TypeScript type system to the strictier OCaml, so creating and maintaining bindings to js libs is mostly manual labor. Compared to plain BuckleScript interop, there are ways to take advantage of reason-to-typescript export in order to at least enforce some consistency when consuming typescript types and functions with redefined types.
Based on this, it seems relatively easy to write a part of my app in reasonml and consume it from typescript thanks to genType, as long as it's something relatively dependency free, but it could be quite difficult to go 100% reasonml if I'm reliant on a ton of js/ts libs with no bs-* bindings available and cannot afford to write them myself.

Closing for now. Feel free to re-open for more discussion.


gl-450-query-statistics-arb

I can't find any reference of GL_ARB_query_statistics_arb
probably it's GL_ARB_pipeline_statistics_query instead, isn't?

Thanks for contributing,
Christophe


Poc

I'm new here, but may I ask why did you close it? It seems like a neat step forward to me...

@dumblob welcome!
Because this is pretty much still in discussion, I opened it on my fork instead: https://github.com/LukeMarlin/docker-mailserver-admin/pull/2
When we'll reach an agreement, I'll make the PR on that official repo. In the meantime, feel free to comment over there (just keep in mind this is not polished at all, it's just to spark discussion!)


feat: added login page

Issue #25 📐

I Ritam Pramanik have worked for #25

Guidelines 🔐
I accept the fact that I have followed the guidelines and have not copied the codes from around the internet

[x] Contribution Guidelines
[x] Code of Conduct

Issue to be closed 🛅

My pull request closes #25

Screenshots 📷
Here are the pictures of changes that I have made 🔽

@Souvikbera1 please review it for confirming the merge

Add authentication in this page .


pipenv installs into python installation and not virtualenv

Issue description
pipenv install installs packages like pytest into PYTHONHOME Location and not the virtualenv
Expected result
pytest is installed into virtualenv and pipenv run pytest works.
Actual result
Installing collected packages: pytest  The scripts py.test.exe and pytest.exe are installed in 'D:\Python36\Scripts' which is not on PATH.    Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location. Successfully installed pytest-4.0.0.
pipenv run pytest results in command pytest not found
Steps to replicate
$ pipenv --support
Pipenv version: '2018.11.14'
Pipenv location: 'd:\\python36\\lib\\site-packages\\pipenv'
Python location: 'd:\\python36\\python.exe'
Python installations found:

3.6.7: D:\Python36\python.exe
3.6.6: D:\Python36-64\python.exe

PEP 508 Information:
{'implementation_name': 'cpython',
 'implementation_version': '3.6.7',
 'os_name': 'nt',
 'platform_machine': 'AMD64',
 'platform_python_implementation': 'CPython',
 'platform_release': '7',
 'platform_system': 'Windows',
 'platform_version': '6.1.7601',
 'python_full_version': '3.6.7',
 'python_version': '3.6',
 'sys_platform': 'win32'}

System environment variables:

ALLUSERSPROFILE
APPDATA
CGROAMINGPATH
CLIENTNAME
COMMONPROGRAMFILES
COMMONPROGRAMFILES(X86)
COMMONPROGRAMW6432
COMPUTERNAME
COMSPEC
DAS_HOME
DSPACE_RTT_TOOLS_2
FP_NO_HOST_CHECK
GOPATH
GOROOT
HOMEDRIVE
HOMEPATH
HTTPS_PROXY
LM_LICENSE_FILE
LOCALAPPDATA
LOGONSERVER
LSFORCEHOST
LSHOST
NUMBER_OF_PROCESSORS
OPENSSL_CONF
OS
PATH
PATHEXT
PLMVIS_82_LIBPATH
PROCESSOR_ARCHITECTURE
PROCESSOR_ARCHITEW6432
PROCESSOR_IDENTIFIER
PROCESSOR_LEVEL
PROCESSOR_REVISION
PROGRAMDATA
PROGRAMFILES
PROGRAMFILES(X86)
PROGRAMW6432
PROMPT
PSMODULEPATH
PUBLIC
RTARCH
RTHOME
SECSPECIALMODE
SESSIONNAME
SILVER_HOME
SIL_USER_TYPE
SYSTEMDRIVE
SYSTEMROOT
TEMP
TERM
TMP
TSK_OPTIONS_FILE_SW160800V6_2R1
UATDATA
USERDNSDOMAIN
USERDOMAIN
USERDOMAIN_ROAMINGPROFILE
USERNAME
USERPROFILE
VS100COMNTOOLS
VS120COMNTOOLS
VS140COMNTOOLS
VS90COMNTOOLS
WINDIR
WINDOWS_TRACING_FLAGS
WINDOWS_TRACING_LOGFILE
PIP_DISABLE_PIP_VERSION_CHECK
PYTHONDONTWRITEBYTECODE
PIP_SHIMS_BASE_MODULE
PIP_PYTHON_PATH
PYTHONFINDER_IGNORE_UNSUPPORTED
PYTHONHOME

Pipenv specific environment variables:
Debug specific environment variables:

PATH: C:\Program Files (x86)\Common Files\Oracle\Java\javapath;%PYTHONHOME%;%PYTHONHOME%\Scripts;D:\Sprachen\Perl\perl\bin\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;l

I believe this is fixed on the master branch — @frostming is this covered by your change to environment targets?

Also can you provide the text of the command you executed and the content of your Pipfile

Sure,
Pipefile
[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[packages]
pyparsing = "*"
pytest = "*"
pytest-mock = "*"
pytest-pythonpath = "*"
pylint = "*"

[dev-packages]

[requires]
python_version = "3.6"

Command:
D:\Python36\scripts\pipenv.exe install -v --python D:\Python36\python.exe

```
Virtualenv already exists!
Removing existing virtualenv...
Creating a virtualenv for this project...
Pipfile: D:\jobs\workspace\project\Pipfile
Using D:\Python36\python.exe (3.6.7) to create virtualenv...
Running virtualenv with interpreter D:\Python36\python.exe
PYTHONHOME is set.  You must activate the virtualenv before using it
Using base prefix 'D:\Python36'
New python executable in C:\Users\user.virtualenvs\project-H6905KSh\Scripts\python.exe
Installing setuptools, pip, wheel...done.
Setting project for project-H6905KSh to D:\jobs\workspace\project
Virtualenv location: C:\Users\user.virtualenvs\project-H6905KSh
Pipfile.lock (5df795) out of date, updating to (c520b6)...
Locking [dev-packages] dependencies...
Locking [packages] dependencies...
Updated Pipfile.lock (c520b6)!
Installing dependencies from Pipfile.lock (c520b6)...
Installing 'astroid==2.0.4 --hash=sha256:292fa429e69d60e4161e7612cb7cc8fa3609e2e309f80c224d93a76d5e7b58be --hash=sha256:c7013d119ec95eb626f7a2011f0b63d0c9a095df9ad06d8507b37084eada1a8d'
$ "C:\Users\user\.virtualenvs\project-H6905KSh\Scripts\pip.exe" install   --verbose  --no-deps  -r "C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-ss9e1eus-requirement.txt" --require-hashes -i https://pypi.org/simple --exists-action w
Installing "atomicwrites==1.2.1; python_version != '3.0.' --hash=sha256:0312ad34fcad8fac3704d441f7b317e50af620823353ec657a53e981f92920c0 --hash=sha256:ec9ae8adaae229e4f8446952d204a3e4b5fdd2d099f9be3aaf556120135fb3ee"
$ "C:\Users\user\.virtualenvs\project-H6905KSh\Scripts\pip.exe" install   --verbose  --no-deps  -r "C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-knjitttk-requirement.txt" --require-hashes -i https://pypi.org/simple --exists-action w
Installing 'attrs==18.2.0 --hash=sha256:10cbf6e27dbce8c30807caf056c8eb50917e0eaafe86347671b57254006c3e69 --hash=sha256:ca4be454458f9dec299268d472aaa5a11f67a4ff70093396e1ceae9c76cf4bbb'
$ "C:\Users\user\.virtualenvs\project-H6905KSh\Scripts\pip.exe" install   --verbose  --no-deps  -r "C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-xbegsfd7-requirement.txt" --require-hashes -i https://pypi.org/simple --exists-action w
Installing "colorama==0.4.0; python_version != '3.0.' --hash=sha256:a3d89af5db9e9806a779a50296b5fdb466e281147c2c235e8225ecc6dbf7bbf3 --hash=sha256:c9b54bebe91a6a803e0772c8561d53f2926bfeb17cd141fbabcb08424086595c"
$ "C:\Users\user\.virtualenvs\project-H6905KSh\Scripts\pip.exe" install   --verbose  --no-deps  -r "C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-1i0cz_ih-requirement.txt" --require-hashes -i https://pypi.org/simple --exists-action w
Installing "isort==4.3.4; python_version != '3.2.' --hash=sha256:1153601da39a25b14ddc54955dbbacbb6b2d19135386699e2ad58517953b34af --hash=sha256:b9c40e9750f3d77e6e4d441d8b0266cf555e7cdabdcff33c4fd06366ca761ef8 --hash=sha256:ec9ef8f4a9bc6f71eec99e1806bfa2de401650d996c59330782b89a5555c1497"
$ "C:\Users\user\.virtualenvs\project-H6905KSh\Scripts\pip.exe" install   --verbose  --no-deps  -r "C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-7ayv_n0v-requirement.txt" --require-hashes -i https://pypi.org/simple --exists-action w
Installing 'lazy-object-proxy==1.3.1 --hash=sha256:0ce34342b419bd8f018e6666bfef729aec3edf62345a53b537a4dcc115746a33 --hash=sha256:1b668120716eb7ee21d8a38815e5eb3bb8211117d9a90b0f8e21722c0758cc39 --hash=sha256:209615b0fe4624d79e50220ce3310ca1a9445fd8e6d3572a896e7f9146bbf019 --hash=sha256:27bf62cb2b1a2068d443ff7097ee33393f8483b570b475db8ebf7e1cba64f088 --hash=sha256:27ea6fd1c02dcc78172a82fc37fcc0992a94e4cecf53cb6d73f11749825bd98b --hash=sha256:2c1b21b44ac9beb0fc848d3993924147ba45c4ebc24be19825e57aabbe74a99e --hash=sha256:2df72ab12046a3496a92476020a1a0abf78b2a7db9ff4dc2036b8dd980203ae6 --hash=sha256:320ffd3de9699d3892048baee45ebfbbf9388a7d65d832d7e580243ade426d2b --hash=sha256:50e3b9a464d5d08cc5227413db0d1c4707b6172e4d4d915c1c70e4de0bbff1f5 --hash=sha256:5276db7ff62bb7b52f77f1f51ed58850e315154249aceb42e7f4c611f0f847ff --hash=sha256:61a6cf00dcb1a7f0c773ed4acc509cb636af2d6337a08f362413c76b2b47a8dd --hash=sha256:6ae6c4cb59f199d8827c5a07546b2ab7e85d262acaccaacd49b62f53f7c456f7 --hash=sha256:7661d401d60d8bf15bb5da39e4dd72f5d764c5aff5a86ef52a042506e3e970ff --hash=sha256:7bd527f36a605c914efca5d3d014170b2cb184723e423d26b1fb2fd9108e264d --hash=sha256:7cb54db3535c8686ea12e9535eb087d32421184eacc6939ef15ef50f83a5e7e2 --hash=sha256:7f3a2d740291f7f2c111d86a1c4851b70fb000a6c8883a59660d95ad57b9df35 --hash=sha256:81304b7d8e9c824d058087dcb89144842c8e0dea6d281c031f59f0acf66963d4 --hash=sha256:933947e8b4fbe617a51528b09851685138b49d511af0b6c0da2539115d6d4514 --hash=sha256:94223d7f060301b3a8c09c9b3bc3294b56b2188e7d8179c762a1cda72c979252 --hash=sha256:ab3ca49afcb47058393b0122428358d2fbe0408cf99f1b58b295cfeb4ed39109 --hash=sha256:bd6292f565ca46dee4e737ebcc20742e3b5be2b01556dafe169f6c65d088875f --hash=sha256:cb924aa3e4a3fb644d0c463cad5bc2572649a6a3f68a7f8e4fbe44aaa6d77e4c --hash=sha256:d0fc7a286feac9077ec52a927fc9fe8fe2fabab95426722be4c953c9a8bede92 --hash=sha256:ddc34786490a6e4ec0a855d401034cbd1242ef186c20d79d2166d6a4bd449577 --hash=sha256:e34b155e36fa9da7e1b7c738ed7767fc9491a62ec6af70fe9da4a057759edc2d --hash=sha256:e5b9e8f6bda48460b7b143c3821b21b452cb3a835e6bbd5dd33aa0c8d3f5137d --hash=sha256:e81ebf6c5ee9684be8f2c87563880f93eedd56dd2b6146d8a725b50b7e5adb0f --hash=sha256:eb91be369f945f10d3a49f5f9be8b3d0b93a4c2be8f8a5b83b0571b8123e0a7a --hash=sha256:f460d1ceb0e4a5dcb2a652db0904224f367c9b3c1470d5a7683c0480e582468b'
$ "C:\Users\user\.virtualenvs\project-H6905KSh\Scripts\pip.exe" install   --verbose  --no-deps  -r "C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-pi92xils-requirement.txt" --require-hashes -i https://pypi.org/simple --exists-action w
Installing 'mccabe==0.6.1 --hash=sha256:ab8a6258860da4b6677da4bd2fe5dc2c659cff31b3ee4f7f5d64e79735b80d42 --hash=sha256:dd8d182285a0fe56bace7f45b5e7d1a6ebcbf524e8f3bd87eb0f125271b8831f'
$ "C:\Users\user\.virtualenvs\project-H6905KSh\Scripts\pip.exe" install   --verbose  --no-deps  -r "C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-7vw4cm6_-requirement.txt" --require-hashes -i https://pypi.org/simple --exists-action w
Installing 'more-itertools==4.3.0 --hash=sha256:c187a73da93e7a8acc0001572aebc7e3c69daf7bf6881a2cea10650bd4420092 --hash=sha256:c476b5d3a34e12d40130bc2f935028b5f636df8f372dc2c1c01dc19681b2039e --hash=sha256:fcbfeaea0be121980e15bc97b3817b5202ca73d0eae185b4550cbfce2a3ebb3d'
$ "C:\Users\user\.virtualenvs\project-H6905KSh\Scripts\pip.exe" install   --verbose  --no-deps  -r "C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-_pj1sbox-requirement.txt" --require-hashes -i https://pypi.org/simple --exists-action w
Installing "pluggy==0.8.0; python_version != '3.0.' --hash=sha256:447ba94990e8014ee25ec853339faf7b0fc8050cdc3289d4d71f7f410fb90095 --hash=sha256:bde19360a8ec4dfd8a20dcb811780a30998101f078fc7ded6162f0076f50508f"
$ "C:\Users\user\.virtualenvs\project-H6905KSh\Scripts\pip.exe" install   --verbose  --no-deps  -r "C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-9x1cazb5-requirement.txt" --require-hashes -i https://pypi.org/simple --exists-action w
Installing "py==1.7.0; python_version != '3.0.*' --hash=sha256:bf92637198836372b520efcba9e020c330123be8ce527e535d185ed4b6f45694 --hash=sha256:e76826342cefe3c3d5f7e8ee4316b80d1dd8a300781612ddbc765c17ba25a6c6"
$ "C:\Users\user\.virtualenvs\project-H6905KSh\Scripts\pip.exe" install   --verbose  --no-deps  -r "C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-htckzrn3-requirement.txt" --require-hashes -i https://pypi.org/simple --exists-action w
Installing 'pylint==2.1.1 --hash=sha256:1d6d3622c94b4887115fe5204982eee66fdd8a951cf98635ee5caee6ec98c3ec --hash=sha256:31142f764d2a7cd41df5196f9933b12b7ee55e73ef12204b648ad7e556c119fb'
$ "C:\Users\user\.virtualenvs\project-H6905KSh\Scripts\pip.exe" install   --verbose  --no-deps  -r "C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-_0zlmqmi-requirement.txt" --require-hashes -i https://pypi.org/simple --exists-action w
Installing 'pyparsing==2.3.0 --hash=sha256:40856e74d4987de5d01761a22d1621ae1c7f8774585acae358aa5c5936c6c90b --hash=sha256:f353aab21fd474459d97b709e527b5571314ee5f067441dc9f88e33eecd96592'
$ "C:\Users\user\.virtualenvs\project-H6905KSh\Scripts\pip.exe" install   --verbose  --no-deps  -r "C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-kg88imxe-requirement.txt" --require-hashes -i https://pypi.org/simple --exists-action w
Installing 'pytest==4.0.0 --hash=sha256:488c842647bbeb350029da10325cb40af0a9c7a2fdda45aeb1dda75b60048ffb --hash=sha256:c055690dfefa744992f563e8c3a654089a6aa5b8092dded9b6fafbd70b2e45a7'
$ "C:\Users\user\.virtualenvs\project-H6905KSh\Scripts\pip.exe" install   --verbose  --no-deps  -r "C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-nspvts6h-requirement.txt" --require-hashes -i https://pypi.org/simple --exists-action w
Installing 'pytest-mock==1.10.0 --hash=sha256:53801e621223d34724926a5c98bd90e8e417ce35264365d39d6c896388dcc928 --hash=sha256:d89a8209d722b8307b5e351496830d5cc5e192336003a485443ae9adeb7dd4c0'
$ "C:\Users\user\.virtualenvs\project-H6905KSh\Scripts\pip.exe" install   --verbose  --no-deps  -r "C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-crl6h3t0-requirement.txt" --require-hashes -i https://pypi.org/simple --exists-action w
Installing 'pytest-pythonpath==0.7.3 --hash=sha256:63fc546ace7d2c845c1ee289e8f7a6362c2b6bae497d10c716e58e253e801d62'
$ "C:\Users\user\.virtualenvs\project-H6905KSh\Scripts\pip.exe" install   --verbose  --no-deps  -r "C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-ltphc3yw-requirement.txt" --require-hashes -i https://pypi.org/simple --exists-action w
Installing 'six==1.11.0 --hash=sha256:70e8a77beed4562e7f14fe23a786b54f6296e34344c23bc42f07b15018ff98e9 --hash=sha256:832dc0e10feb1aa2c68dcc57dbb658f1c7e65b9b61af69048abc87a2db00a0eb'
$ "C:\Users\user\.virtualenvs\project-H6905KSh\Scripts\pip.exe" install   --verbose  --no-deps  -r "C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-w9lffomf-requirement.txt" --require-hashes -i https://pypi.org/simple --exists-action w
Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
Config variable 'WITH_PYMALLOC' is unset, Python ABI tag may be incorrect
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-ephem-wheel-cache-jg5txqn5
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-req-tracker-jgeyl51f
Created requirements tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-jgeyl51f'
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-install-by9h4wls
Requirement already satisfied: astroid==2.0.4 in d:\python36\lib\site-packages (from -r C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-ss9e1eus-requirement.txt (line 1)) (2.0.4)
Since it is already installed, we are trusting this package without checking its hash. To ensure a completely repeatable environment, install into an empty virtualenv.
Cleaning up...
Removed build tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-jgeyl51f'
You are using pip version 18.0, however version 18.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
Config variable 'WITH_PYMALLOC' is unset, Python ABI tag may be incorrect
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-ephem-wheel-cache-t7np6gkp
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-req-tracker-uz8_1f2i
Created requirements tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-uz8_1f2i'
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-install-u_r4rnog
Requirement already satisfied: atomicwrites==1.2.1 in d:\python36\lib\site-packages (from -r C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-knjitttk-requirement.txt (line 1)) (1.2.1)
Since it is already installed, we are trusting this package without checking its hash. To ensure a completely repeatable environment, install into an empty virtualenv.
Cleaning up...
Removed build tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-uz8_1f2i'
You are using pip version 18.0, however version 18.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
Config variable 'WITH_PYMALLOC' is unset, Python ABI tag may be incorrect
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-ephem-wheel-cache-qv6l0zfk
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-req-tracker-at8zuww7
Created requirements tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-at8zuww7'
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-install-vt0uli9t
Requirement already satisfied: attrs==18.2.0 in d:\python36\lib\site-packages (from -r C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-xbegsfd7-requirement.txt (line 1)) (18.2.0)
Since it is already installed, we are trusting this package without checking its hash. To ensure a completely repeatable environment, install into an empty virtualenv.
Cleaning up...
Removed build tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-at8zuww7'
You are using pip version 18.0, however version 18.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
Config variable 'WITH_PYMALLOC' is unset, Python ABI tag may be incorrect
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-ephem-wheel-cache-c37et1or
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-req-tracker-mhvyd5kr
Created requirements tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-mhvyd5kr'
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-install-mtu3isp0
Requirement already satisfied: colorama==0.4.0 in d:\python36\lib\site-packages (from -r C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-1i0cz_ih-requirement.txt (line 1)) (0.4.0)
Since it is already installed, we are trusting this package without checking its hash. To ensure a completely repeatable environment, install into an empty virtualenv.
Cleaning up...
Removed build tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-mhvyd5kr'
You are using pip version 18.0, however version 18.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
Config variable 'WITH_PYMALLOC' is unset, Python ABI tag may be incorrect
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-ephem-wheel-cache-bid49uv2
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-req-tracker-3mtjlybf
Created requirements tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-3mtjlybf'
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-install-yimdyd6r
Requirement already satisfied: isort==4.3.4 in d:\python36\lib\site-packages (from -r C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-7ayv_n0v-requirement.txt (line 1)) (4.3.4)
Since it is already installed, we are trusting this package without checking its hash. To ensure a completely repeatable environment, install into an empty virtualenv.
Cleaning up...
Removed build tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-3mtjlybf'
You are using pip version 18.0, however version 18.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
Config variable 'WITH_PYMALLOC' is unset, Python ABI tag may be incorrect
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-ephem-wheel-cache-g05r_56u
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-req-tracker-tnfjc4b1
Created requirements tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-tnfjc4b1'
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-install-jb4gvjpm
Requirement already satisfied: lazy-object-proxy==1.3.1 in d:\python36\lib\site-packages (from -r C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-pi92xils-requirement.txt (line 1)) (1.3.1)
Since it is already installed, we are trusting this package without checking its hash. To ensure a completely repeatable environment, install into an empty virtualenv.
Cleaning up...
Removed build tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-tnfjc4b1'
You are using pip version 18.0, however version 18.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
Config variable 'WITH_PYMALLOC' is unset, Python ABI tag may be incorrect
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-ephem-wheel-cache-11gxf1p4
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-req-tracker-0texez96
Created requirements tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-0texez96'
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-install-sipig2qg
Requirement already satisfied: mccabe==0.6.1 in d:\python36\lib\site-packages (from -r C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-7vw4cm6_-requirement.txt (line 1)) (0.6.1)
Since it is already installed, we are trusting this package without checking its hash. To ensure a completely repeatable environment, install into an empty virtualenv.
Cleaning up...
Removed build tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-0texez96'
You are using pip version 18.0, however version 18.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
Config variable 'WITH_PYMALLOC' is unset, Python ABI tag may be incorrect
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-ephem-wheel-cache-ndslgunt
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-req-tracker-88rud541
Created requirements tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-88rud541'
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-install-4193qp9d
Requirement already satisfied: more-itertools==4.3.0 in d:\python36\lib\site-packages (from -r C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-_pj1sbox-requirement.txt (line 1)) (4.3.0)
Since it is already installed, we are trusting this package without checking its hash. To ensure a completely repeatable environment, install into an empty virtualenv.
Cleaning up...
Removed build tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-88rud541'
You are using pip version 18.0, however version 18.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
Config variable 'WITH_PYMALLOC' is unset, Python ABI tag may be incorrect
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-ephem-wheel-cache-r7m9nsom
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-req-tracker-lulap3tu
Created requirements tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-lulap3tu'
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-install-qs_owsua
Requirement already satisfied: pluggy==0.8.0 in d:\python36\lib\site-packages (from -r C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-9x1cazb5-requirement.txt (line 1)) (0.8.0)
Since it is already installed, we are trusting this package without checking its hash. To ensure a completely repeatable environment, install into an empty virtualenv.
Cleaning up...
Removed build tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-lulap3tu'
You are using pip version 18.0, however version 18.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
Config variable 'WITH_PYMALLOC' is unset, Python ABI tag may be incorrect
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-ephem-wheel-cache-g0hcy322
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-req-tracker-g23no13y
Created requirements tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-g23no13y'
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-install-yis2gtjn
Requirement already satisfied: py==1.7.0 in d:\python36\lib\site-packages (from -r C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-htckzrn3-requirement.txt (line 1)) (1.7.0)
Since it is already installed, we are trusting this package without checking its hash. To ensure a completely repeatable environment, install into an empty virtualenv.
Cleaning up...
Removed build tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-g23no13y'
You are using pip version 18.0, however version 18.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
Config variable 'WITH_PYMALLOC' is unset, Python ABI tag may be incorrect
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-ephem-wheel-cache-n6wt85_z
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-req-tracker-or1rvrz4
Created requirements tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-or1rvrz4'
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-install-c_1qc8w7
Requirement already satisfied: pylint==2.1.1 in d:\python36\lib\site-packages (from -r C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-_0zlmqmi-requirement.txt (line 1)) (2.1.1)
Since it is already installed, we are trusting this package without checking its hash. To ensure a completely repeatable environment, install into an empty virtualenv.
Cleaning up...
Removed build tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-or1rvrz4'
You are using pip version 18.0, however version 18.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
Config variable 'WITH_PYMALLOC' is unset, Python ABI tag may be incorrect
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-ephem-wheel-cache-ukb3mywt
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-req-tracker-1qffukoo
Created requirements tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-1qffukoo'
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-install-7shl14it
Requirement already satisfied: pyparsing==2.3.0 in d:\python36\lib\site-packages (from -r C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-kg88imxe-requirement.txt (line 1)) (2.3.0)
Since it is already installed, we are trusting this package without checking its hash. To ensure a completely repeatable environment, install into an empty virtualenv.
Cleaning up...
Removed build tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-1qffukoo'
You are using pip version 18.0, however version 18.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
Config variable 'WITH_PYMALLOC' is unset, Python ABI tag may be incorrect
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-ephem-wheel-cache-ffyiup5x
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-req-tracker-cewyl6gr
Created requirements tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-cewyl6gr'
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-install-zcp40pzx
Requirement already satisfied: pytest==4.0.0 in d:\python36\lib\site-packages (from -r C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-nspvts6h-requirement.txt (line 1)) (4.0.0)
Since it is already installed, we are trusting this package without checking its hash. To ensure a completely repeatable environment, install into an empty virtualenv.
Cleaning up...
Removed build tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-cewyl6gr'
You are using pip version 18.0, however version 18.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
Config variable 'WITH_PYMALLOC' is unset, Python ABI tag may be incorrect
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-ephem-wheel-cache-o_9_ldg5
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-req-tracker-pzorh01p
Created requirements tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-pzorh01p'
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-install-80xb0tpt
Requirement already satisfied: pytest-mock==1.10.0 in d:\python36\lib\site-packages (from -r C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-crl6h3t0-requirement.txt (line 1)) (1.10.0)
Since it is already installed, we are trusting this package without checking its hash. To ensure a completely repeatable environment, install into an empty virtualenv.
Cleaning up...
Removed build tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-pzorh01p'
You are using pip version 18.0, however version 18.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
Config variable 'WITH_PYMALLOC' is unset, Python ABI tag may be incorrect
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-ephem-wheel-cache-2lcds5vd
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-req-tracker-8og9tl6j
Created requirements tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-8og9tl6j'
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-install-bb428bub
Requirement already satisfied: pytest-pythonpath==0.7.3 in d:\python36\lib\site-packages (from -r C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-ltphc3yw-requirement.txt (line 1)) (0.7.3)
Since it is already installed, we are trusting this package without checking its hash. To ensure a completely repeatable environment, install into an empty virtualenv.
Cleaning up...
Removed build tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-8og9tl6j'
You are using pip version 18.0, however version 18.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
Config variable 'WITH_PYMALLOC' is unset, Python ABI tag may be incorrect
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-ephem-wheel-cache-s8uwz6mp
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-req-tracker-_6so9wri
Created requirements tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-_6so9wri'
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-install-s7f76zcl
Requirement already satisfied: six==1.11.0 in d:\python36\lib\site-packages (from -r C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-w9lffomf-requirement.txt (line 1)) (1.11.0)
Since it is already installed, we are trusting this package without checking its hash. To ensure a completely repeatable environment, install into an empty virtualenv.
Cleaning up...
Removed build tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-_6so9wri'
You are using pip version 18.0, however version 18.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
Installing "typed-ast==1.1.0; python_version < '3.7' and implementation_name == 'cpython' --hash=sha256:0948004fa228ae071054f5208840a1e88747a357ec1101c17217bfe99b299d58 --hash=sha256:10703d3cec8dcd9eef5a630a04056bbc898abc19bac5691612acba7d1325b66d --hash=sha256:1f6c4bd0bdc0f14246fd41262df7dfc018d65bb05f6e16390b7ea26ca454a291 --hash=sha256:25d8feefe27eb0303b73545416b13d108c6067b846b543738a25ff304824ed9a --hash=sha256:29464a177d56e4e055b5f7b629935af7f49c196be47528cc94e0a7bf83fbc2b9 --hash=sha256:2e214b72168ea0275efd6c884b114ab42e316de3ffa125b267e732ed2abda892 --hash=sha256:3e0d5e48e3a23e9a4d1a9f698e32a542a4a288c871d33ed8df1b092a40f3a0f9 --hash=sha256:519425deca5c2b2bdac49f77b2c5625781abbaf9a809d727d3a5596b30bb4ded --hash=sha256:57fe287f0cdd9ceaf69e7b71a2e94a24b5d268b35df251a88fef5cc241bf73aa --hash=sha256:668d0cec391d9aed1c6a388b0d5b97cd22e6073eaa5fbaa6d2946603b4871efe --hash=sha256:68ba70684990f59497680ff90d18e756a47bf4863c604098f10de9716b2c0bdd --hash=sha256:6de012d2b166fe7a4cdf505eee3aaa12192f7ba365beeefaca4ec10e31241a85 --hash=sha256:79b91ebe5a28d349b6d0d323023350133e927b4de5b651a8aa2db69c761420c6 --hash=sha256:8550177fa5d4c1f09b5e5f524411c44633c80ec69b24e0e98906dd761941ca46 --hash=sha256:898f818399cafcdb93cbbe15fc83a33d05f18e29fb498ddc09b0214cdfc7cd51 --hash=sha256:94b091dc0f19291adcb279a108f5d38de2430411068b219f41b343c03b28fb1f --hash=sha256:a26863198902cda15ab4503991e8cf1ca874219e0118cbf07c126bce7c4db129 --hash=sha256:a8034021801bc0440f2e027c354b4eafd95891b573e12ff0418dec385c76785c --hash=sha256:bc978ac17468fe868ee589c795d06777f75496b1ed576d308002c8a5756fb9ea --hash=sha256:c05b41bc1deade9f90ddc5d988fe506208019ebba9f2578c622516fd201f5863 --hash=sha256:c9b060bd1e5a26ab6e8267fd46fc9e02b54eb15fffb16d112d4c7b1c12987559 --hash=sha256:edb04bdd45bfd76c8292c4d9654568efaedf76fe78eb246dde69bdb13b2dad87 --hash=sha256:f19f2a4f547505fe9072e15f6f4ae714af51b5a681a97f187971f50c283193b6"
$ "C:\Users\user\.virtualenvs\project-H6905KSh\Scripts\pip.exe" install   --verbose  --no-deps  -r "C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-hgsccohy-requirement.txt" --require-hashes -i https://pypi.org/simple --exists-action w
Installing 'wrapt==1.10.11 --hash=sha256:d4d560d479f2c21e1b5443bbd15fe7ec4b37fe7e53d335d3b9b0a7b1226fe3c6'
$ "C:\Users\user\.virtualenvs\project-H6905KSh\Scripts\pip.exe" install   --verbose  --no-deps  -r "C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-x7di3x3u-requirement.txt" --require-hashes -i https://pypi.org/simple --exists-action w
Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
Config variable 'WITH_PYMALLOC' is unset, Python ABI tag may be incorrect
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-ephem-wheel-cache-4y58hgef
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-req-tracker-v9k0wccj
Created requirements tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-v9k0wccj'
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-install-h8_7xt8b
Requirement already satisfied: typed-ast==1.1.0 in d:\python36\lib\site-packages (from -r C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-hgsccohy-requirement.txt (line 1)) (1.1.0)
Since it is already installed, we are trusting this package without checking its hash. To ensure a completely repeatable environment, install into an empty virtualenv.
Cleaning up...
Removed build tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-v9k0wccj'
You are using pip version 18.0, however version 18.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
Config variable 'WITH_PYMALLOC' is unset, Python ABI tag may be incorrect
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-ephem-wheel-cache-ixrbnavu
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-req-tracker-fl8ed_pl
Created requirements tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-fl8ed_pl'
Created temporary directory: C:\Users\user\AppData\Local\Temp\pip-install-o9jebry_
Requirement already satisfied: wrapt==1.10.11 in d:\python36\lib\site-packages (from -r C:\Users\user\AppData\Local\Temp\pipenv-yf7oqrzb-requirements\pipenv-x7di3x3u-requirement.txt (line 1)) (1.10.11)
Since it is already installed, we are trusting this package without checking its hash. To ensure a completely repeatable environment, install into an empty virtualenv.
Cleaning up...
Removed build tracker 'C:\Users\user\AppData\Local\Temp\pip-req-tracker-fl8ed_pl'
</details>

I compared the behavior with virtualenv.
@techalchemy When PYTHONHOME is set, using $(VENV_PATH)/bin/pip install ... won't do the trick. Maybe we should shade the PYTHONHOME temporary inside virtualenv, shell, run, etc.?

I'm not totally certain whats best here, my initial instinct was yeah to just unset it the way we do with PIP_USER -- just check if allow_global or system is set, and if not, just unset PYTHONHOME? I might override it in pipenv.environment.Environment.activated() anyway...

I use this code to install pipenv
$ brew install pipenv
it works with me fine try this code.


[Question] How to uncheck a list item checkbox

I have a list of items with a checkbox.
<f7-list-item
  v-for="(item, key) in items" :key="key"
  :title="item.title"
  checkbox checked
  :name="`item-${key}`"
  @change="handleItemChecked(key)" />

On select, I perform the database write ... in case there is an error, I want to uncheck the item again. What not worked is the following:
handleItemChecked(key) {
  this.$$(`input[name=item-${key}`).attr('checked', false)
}

Has anybody an idea how I could do that with the key as reference?

It should be .prop instead of .attr


Update Netty to 4.1.51.Final

This PR proposes to update Netty to its latest bugfix 4.1.51.Final.

Thanks, but we have since updated to 4.1.52.Final.


fix: Reorder Unified.js plugins to fix #1132

Fixes #1132
Before:

After:

Pretty sure toc was broken before 😅.
By syntax highlighting do you mean in code blocks?

yeah code blocks that have latex as the language should still work

Renders to:

TOC is still broken:
before:

After:

The problem with the TOC is that it is generated by unifiedjs plugin but it is not mdast. When it is made:

Only the text is gets forwarded to the TOC generator and not the whole ast node.
The TOC element does not support ast

I have crated a new issue to track the bug with TOC #1143


--ignore-errors and --max-retries do nothing against ConnectionRefusedError

Hello,
I've tried Waybackpack, and the Internet Archive sometimes refuses connexions for apparently no reason, as the refused link can be openned in the browser.
I hoped that --ignore-errors would help Waybackpack ignore that error; and that --max-retries would retry to connect; but to no avail.
Best regards.

Hi @malespiaut, and thanks for your interest in this tool. Are you able to provide a specific command that raises this issue, so that it can be investigated / debugged?

Getting snapshot pages................../usr/lib/ruby/3.1.0/socket.rb:1214:in __connect_nonblock': Failed to open TCP connection to web.archive.org:443 (Connection refused - connect(2) for <IP_ADDRESS>:443) (Errno::ECONNREFUSED)         from /usr/lib/ruby/3.1.0/socket.rb:1214:in connect_nonblock'
from /usr/lib/ruby/3.1.0/socket.rb:56:in connect_internal'         from /usr/lib/ruby/3.1.0/socket.rb:137:in connect'
from /usr/lib/ruby/3.1.0/socket.rb:642:in block in tcp'         from /usr/lib/ruby/3.1.0/socket.rb:227:in each'
from /usr/lib/ruby/3.1.0/socket.rb:227:in foreach'         from /usr/lib/ruby/3.1.0/socket.rb:632:in tcp'
from /usr/lib/ruby/3.1.0/net/http.rb:998:in connect'         from /usr/lib/ruby/3.1.0/net/http.rb:976:in do_start'
from /usr/lib/ruby/3.1.0/net/http.rb:965:in start'         from /usr/lib/ruby/3.1.0/open-uri.rb:323:in open_http'
from /usr/lib/ruby/3.1.0/open-uri.rb:741:in buffer_open'         from /usr/lib/ruby/3.1.0/open-uri.rb:212:in block in open_loop'
from /usr/lib/ruby/3.1.0/open-uri.rb:210:in catch'         from /usr/lib/ruby/3.1.0/open-uri.rb:210:in open_loop'
from /usr/lib/ruby/3.1.0/open-uri.rb:151:in open_uri'         from /usr/lib/ruby/3.1.0/open-uri.rb:721:in open'
from /var/lib/gems/3.1.0/gems/wayback_machine_downloader-2.3.1/lib/wayback_machine_downloader/archive_api.rb:13:in get_raw_list_from_api'         from /var/lib/gems/3.1.0/gems/wayback_machine_downloader-2.3.1/lib/wayback_machine_downloader.rb:92:in block in get_all_snapshots_to_consider'
from /var/lib/gems/3.1.0/gems/wayback_machine_downloader-2.3.1/lib/wayback_machine_downloader.rb:91:in times'         from /var/lib/gems/3.1.0/gems/wayback_machine_downloader-2.3.1/lib/wayback_machine_downloader.rb:91:in get_all_snapshots_to_consider'
from /var/lib/gems/3.1.0/gems/wayback_machine_downloader-2.3.1/lib/wayback_machine_downloader.rb:105:in get_file_list_curated'         from /var/lib/gems/3.1.0/gems/wayback_machine_downloader-2.3.1/lib/wayback_machine_downloader.rb:164:in get_file_list_by_timestamp'
from /var/lib/gems/3.1.0/gems/wayback_machine_downloader-2.3.1/lib/wayback_machine_downloader.rb:309:in file_list_by_timestamp'         from /var/lib/gems/3.1.0/gems/wayback_machine_downloader-2.3.1/lib/wayback_machine_downloader.rb:192:in download_files'
from /var/lib/gems/3.1.0/gems/wayback_machine_downloader-2.3.1/bin/wayback_machine_downloader:72:in <top (required)>'         from /usr/local/bin/wayback_machine_downloader:25:in load'
from /usr/local/bin/wayback_machine_downloader:25:in <main>' /usr/lib/ruby/3.1.0/socket.rb:1214:in __connect_nonblock': Connection refused - connect(2) for <IP_ADDRESS>:443 (Errno::ECONNREFUSED)
from /usr/lib/ruby/3.1.0/socket.rb:1214:in connect_nonblock'         from /usr/lib/ruby/3.1.0/socket.rb:56:in connect_internal'
from /usr/lib/ruby/3.1.0/socket.rb:137:in connect'         from /usr/lib/ruby/3.1.0/socket.rb:642:in block in tcp'
from /usr/lib/ruby/3.1.0/socket.rb:227:in each'         from /usr/lib/ruby/3.1.0/socket.rb:227:in foreach'
from /usr/lib/ruby/3.1.0/socket.rb:632:in tcp'         from /usr/lib/ruby/3.1.0/net/http.rb:998:in connect'
from /usr/lib/ruby/3.1.0/net/http.rb:976:in do_start'         from /usr/lib/ruby/3.1.0/net/http.rb:965:in start'
from /usr/lib/ruby/3.1.0/open-uri.rb:323:in open_http'         from /usr/lib/ruby/3.1.0/open-uri.rb:741:in buffer_open'
from /usr/lib/ruby/3.1.0/open-uri.rb:212:in block in open_loop'         from /usr/lib/ruby/3.1.0/open-uri.rb:210:in catch'
from /usr/lib/ruby/3.1.0/open-uri.rb:210:in open_loop'         from /usr/lib/ruby/3.1.0/open-uri.rb:151:in open_uri'
from /usr/lib/ruby/3.1.0/open-uri.rb:721:in open'         from /var/lib/gems/3.1.0/gems/wayback_machine_downloader-2.3.1/lib/wayback_machine_downloader/archive_api.rb:13:in get_raw_list_from_api'
from /var/lib/gems/3.1.0/gems/wayback_machine_downloader-2.3.1/lib/wayback_machine_downloader.rb:92:in block in get_all_snapshots_to_consider'         from /var/lib/gems/3.1.0/gems/wayback_machine_downloader-2.3.1/lib/wayback_machine_downloader.rb:91:in times'
from /var/lib/gems/3.1.0/gems/wayback_machine_downloader-2.3.1/lib/wayback_machine_downloader.rb:91:in get_all_snapshots_to_consider'         from /var/lib/gems/3.1.0/gems/wayback_machine_downloader-2.3.1/lib/wayback_machine_downloader.rb:105:in get_file_list_curated'
from /var/lib/gems/3.1.0/gems/wayback_machine_downloader-2.3.1/lib/wayback_machine_downloader.rb:164:in get_file_list_by_timestamp'         from /var/lib/gems/3.1.0/gems/wayback_machine_downloader-2.3.1/lib/wayback_machine_downloader.rb:309:in file_list_by_timestamp'
from /var/lib/gems/3.1.0/gems/wayback_machine_downloader-2.3.1/lib/wayback_machine_downloader.rb:192:in download_files'         from /var/lib/gems/3.1.0/gems/wayback_machine_downloader-2.3.1/bin/wayback_machine_downloader:72:in <top (required)>'
from /usr/local/bin/wayback_machine_downloader:25:in load'         from /usr/local/bin/wayback_machine_downloader:25:in '


ERROR: An error occurred during the fetch of repository 'rules_java'

1.env:
ubuntu cpu
2.option:
bazel run --define MEDIAPIPE_DISABLE_GPU=1  mediapipe/examples/desktop/hello_world:hello_world
3.errors:
INFO: Repository rules_java instantiated at:
no stack (--record_rule_instantiation_callstack not enabled)
Repository rule http_archive defined at:
/home/ctt/.cache/bazel/_bazel_ctt/1fabb8f99ae892e3c1f6b539c83c35e9/external/bazel_tools/tools/build_defs/repo/http.bzl:336:31: in
WARNING: Download from https://mirror.bazel.build/github.com/bazelbuild/rules_java/archive/7cf3cefd652008d0a64a419c34c13bdca6c8f178.zip failed: class java.io.IOException Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Authorization Required"
WARNING: Download from https://github.com/bazelbuild/rules_java/archive/7cf3cefd652008d0a64a419c34c13bdca6c8f178.zip failed: class java.io.IOException Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Authorization Required"
ERROR: An error occurred during the fetch of repository 'rules_java':
java.io.IOException: Error downloading [https://mirror.bazel.build/github.com/bazelbuild/rules_java/archive/7cf3cefd652008d0a64a419c34c13bdca6c8f178.zip, https://github.com/bazelbuild/rules_java/archive/7cf3cefd652008d0a64a419c34c13bdca6c8f178.zip] to /home/ctt/.cache/bazel/_bazel_ctt/1fabb8f99ae892e3c1f6b539c83c35e9/external/rules_java/7cf3cefd652008d0a64a419c34c13bdca6c8f178.zip: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Authorization Required"
ERROR: While resolving toolchains for target //mediapipe/examples/desktop/hello_world:hello_world: invalid registered toolchain '@bazel_tools//tools/jdk:all': while parsing '@bazel_tools//tools/jdk:all': no such package '@rules_java//java': java.io.IOException: Error downloading [https://mirror.bazel.build/github.com/bazelbuild/rules_java/archive/7cf3cefd652008d0a64a419c34c13bdca6c8f178.zip, https://github.com/bazelbuild/rules_java/archive/7cf3cefd652008d0a64a419c34c13bdca6c8f178.zip] to /home/ctt/.cache/bazel/_bazel_ctt/1fabb8f99ae892e3c1f6b539c83c35e9/external/rules_java/7cf3cefd652008d0a64a419c34c13bdca6c8f178.zip: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Authorization Required"
ERROR: Analysis of target '//mediapipe/examples/desktop/hello_world:hello_world' failed; build aborted: invalid registered toolchain '@bazel_tools//tools/jdk:all': while parsing '@bazel_tools//tools/jdk:all': no such package '@rules_java//java': java.io.IOException: Error downloading [https://mirror.bazel.build/github.com/bazelbuild/rules_java/archive/7cf3cefd652008d0a64a419c34c13bdca6c8f178.zip, https://github.com/bazelbuild/rules_java/archive/7cf3cefd652008d0a64a419c34c13bdca6c8f178.zip] to /home/ctt/.cache/bazel/_bazel_ctt/1fabb8f99ae892e3c1f6b539c83c35e9/external/rules_java/7cf3cefd652008d0a64a419c34c13bdca6c8f178.zip: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Authorization Required"
problem:
4.I Manual download rules_java packets，but the error  still apear.
I cannot find rules_java in WORKSPACE,where need rules_java?
what can I do about the error?

the issue no longer exists，thank you very much


Unable to add msdyn_purchaseorderbill to Solution package

When trying to add an existing table to my solution package I am unable to add the Bills table to it. The schema name is called msdyn_purchaseorderbill and does not appear in the search either.

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

ID: 5b903798-2033-be36-079a-babe7586981e
Version Independent ID: d588611a-a950-134e-6738-10e8f3899f25
Content: Tables and metadata in Microsoft Dataverse - Power Apps
Content Source: powerapps-docs/maker/data-platform/create-edit-metadata.md
Service: powerapps
GitHub Login: @Mattp123
Microsoft Alias: matp

@gregdegruy - Is the table a managed table? If so, you won't be able to add it to a solution. Closing issue.


Use oidc-client

Hi!
Thanks for your work on this and your blog - they have both been a great resource for me in dealing with auth in ng2.
Not sure if you are actually trying to document how to implement the entire OIDC spec yourself. If not, it would be great to use the official" oidc-client. Any plans for that? That way we would get a lot of "freebies", like token renewal, token validation, better fragment handling...
https://github.com/IdentityModel/oidc-client-js

Hi Thanks
Ye , the oidc-client is a cool library, looks really good. At present, I have no plans for this, I wanted to implement a log out first, and then the database for the users.
Greetings Damien

Hi @pontusr
@jmurphzyo has a good repo here:
https://github.com/jmurphzyo/Angular2OidcClient
Is it ok to close this?
Greetings Damien

Absolutely - we have it working fine since some time using the oidc-client-js library, very good library.


Switch to django storages

Removing the custom backend storage code and replacing it with django storages seems advantageous.

Filed this issue in the master repo.  worth looking at if this is relevant.