text:
Selection area is invisible after update to >= 1.5

Do you want to request a feature or report a bug?
a bug
What is the current behavior?
After updating Selection to any version, greater then 0.1.4, I do not see the selection area on selection.
If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior?
It is quite difficult to extract the page I'm using Selection on out of the whole project.
But it seems to me that change is behaviour is caused by the that._clippingElement added after 0.1.4
How it worked before (v0.1.0):

How it works now (v0.1.5, same on 0.2.1):

Are there any restrictions on the style of html/body tags?
Your environment:
Selection-version: 0.1.5
Browser-version:  Chrome Version 73.0.3683.103
Operating-system:  macOS Mojave 10.14.4

I'm not aware of any, there was #29 where selectables was removed. The html and body  elements shouldn't be used as boundaries since selectionjs should be restricted to a specific area.
No problem, but cuold you provide your selection.js config? I'll try to reproduce it.
_clippingElement is used to restrict the visible area if the container element is scrollable.
Minor version indicated some kind of braking changes, I'll try to fix these as soon as possible :)

Wow, that was fast!
Thank you for the reply.
My config is as follows:
const selectionOptions = {

            class: 'policy-consumers-selection-area',

            selectables: ['.policy-consumers-list__consumer'],
            singleClick: false, // handled by the ng-click callback
            disableTouch: true,
            boundaries: ['.policies-editor-content__right', '.policies-editor-footer__right'],

            onSelect(evt) {
                // Check if clicked element is already selected
                const selected = evt.target.classList.contains(selectedConsumerClass);

                if (!evt.originalEvent.shiftKey) {
                    // Remove class from every element which is selected
                    evt.selectedElements.forEach(s => s.classList.remove(selectedConsumerClass));

                    // Clear previous selection
                    this.clearSelection();
                }

                if (selected) {
                    // Unselect element
                    evt.target.classList.remove(selectedConsumerClass);
                    this.removeFromSelection(evt.target);
                } else {
                    // Select element
                    evt.target.classList.add(selectedConsumerClass);
                    this.keepSelection();
                }
            },

            onStart(evt) {
                if (vm.dragStarted) {
                    // selection.cancel() is a wrapper
                    // for the selection._onTapStop()
                    // which throws an error almost every time (due to a bug)
                    this._onTapStop(evt);

                    const areaEl = evt.areaElement;

                    if (areaEl) {
                        areaEl.hidden = true;

                        $timeout(() => {
                            areaEl.hidden = false;
                        });
                    }

                    return;
                }

                // Remove class if the user don't pressed the shift key
                if (!evt.originalEvent.shiftKey) {
                    vm.deselectSelectedConsumers();
                    this.clearSelection();
                }
            },

            onStop(evt) {
                [...evt.selectedElements].forEach(x => {
                    const $e = angular.element(x);

                    const consumer = _.get(
                        vm,
                        [
                            'policiesToShowConsumersFrom',
                            Number($e.attr('policy-idx')),
                            $e.attr('item-prop'),
                            Number($e.attr('item-idx'))
                        ]
                    );

                    if (!consumer) {
                        return;
                    }

                    const consumerId = consumer[constants.ID_PROP_BY_POLICY_PROP[$e.attr('item-prop')]];

                    consumer.isSelected = !consumer.isSelected;

                    if (consumer.isSelected) {
                        vm.selectedConsumers[consumerId] = consumer;
                        vm.selectedConsumersCount++;
                    } else {
                        delete vm.selectedConsumers[consumerId];
                        vm.selectedConsumersCount--;
                    }
                });

                this.clearSelection();

                if ($scope.$root.$$phase !== '$apply' && $scope.$root.$$phase !== '$digest') {
                    $scope.$apply();
                }
            }
        };

and .policy-consumers-selection-area:
.policy-consumers-selection-area {
    background: rgba(0, 0, 255, 0.1);
    border-radius: 0.1em;
    border: 0.05em solid rgba(0, 0, 255, 0.2);
    z-index: 20;
}

Your lib is really awesome, by the way.

You're welcome :)
Okay, that's strange... If mounted, could you send me a screenshot of the selection-area container which is responsible for the clipping? After this I can investigate why it's clipped / invisible :) Like so:

red - Clipping element
green - Actual selection area

Here's the clipping element on page load:

And here it is after selecting a bunch of elements:

Selection area after selecting a bunch of elements:

I can provide you with a remote access to the working demo if that's ok

Yeah, solving this problem directly on the application itself would be the fastest way to examine the problem. This would be great! Furthermore, if the second image was taken after a selection (the area element has display: none), there's at the first view nothing suspicious in your Environment which would cause this problem.

I think I've got it working. Please try to open the following URL: demo.selection.keenetic.limited.
If it opens successfully (that can take a bit of time & reloads) use selection as login and as password.
I use Selection on the second tab ("Policy bindings") of the controlPanel/policies page.

This is a temporary build, living on my machine. I can make a more permanent solution if this one is too hard to use. Thank you once again for wanting to help.

Well, thank you for providing this demo and great communication to find it :) I found the problem, the clipping area don't have any z-index property, so the applied z-index on the selection-area element don't even take effect. After adding z-index: 1 to the clipping element it works.
Until I published a new version (will be very soon since this looks like a serious bug to me) you can use this piece of code in your selectionjs config to fix this:
onStart({selection}) {
        selection._clippingElement.style.zIndex = 1;
}

Well, thank you for providing this demo and great communication to find it :) I found the problem, the clipping area don't have any z-index property, so the applied z-index on the selection-area element don't even take effect. After adding z-index: 1 to the clipping element it works.
Until I published a new version (will be very soon since this looks like a serious bug to me) you can use this piece of code in your selectionjs config to fix this:
onStart({selection}) {
        selection._clippingElement.style.zIndex = 1;
}

WoW! This is so great ^_^
Thank you so much. I can't express how excited I am 🔥

Oh, GitHub discovered the fix-commit: dd9926bae52dad5f3c8eeb5a026b9c89dca4bdaa :D

@dsechin Thought I'll inform you I published v0.2.2 where this fix takes action :)

@Simonwep I know, that this issue is closed, but I would like to point out that I get the same behavior in my setup with the latest release.
I found a simple fix for it: wrap zIndex value in quotes:
            css(that._clippingElement, {
                overflow: 'hidden',
                position: 'fixed',
                transform: 'translate3d(0, 0, 0)', // https://stackoverflow.com/a/38268846
                pointerEvents: 'none',
                zIndex: '1' // <----------------------
            });

This way it work perfectly. Hope this helps.

Huh, now this is strange, the value of zIndex should be an integer as mentioned here in the official w3 draft 🤔
Is there any way to get hand on a reproduction in a JSFiddle? Because, even if the type for zIndex is still integer, if you use style.zIndex = '1' gives the same result as style.zIndex = 1.
Okay this is an actual a bug in the .css function. If I pass a integer in it it will get unified (with px as standard). So it'd result in zIndex: 1px which is invalid.
I'll fix this later today and roll out 1.4.1, I should pay attention to how my own utils work 😅

@dsechin Fixed in 5539f8b :) I've published 1.4.1 where this fix is applied!

@dsechin Fixed in 5539f8b :) I've published 1.4.1 where this fix is applied!

Thank you for the quick fix! ^_^

authors: Simonwep dsechin

repo: Simonwep/selection


text:
可以支持更多客户端吗？

utorrent、deluge、frostwire系统资源比较低的客户端
tixati 、bigly bt 可以聊天的客户端

感谢反馈!

出于技术限制, 部分客户端无法支持;
出于精力及客户端流行度原因, 部分客户端无人解决支持问题;

Nexusphp本来就支持Azureus，Az在2017年停更之后，辞职员工另外写了个一模一样界面的开源Bigly BT，并非没有PT站点使用，Unit3d和馒头、Hdarea、象岛ptvicomo、blutopia和hdtorrent都支持这个软件，谈不上没人使用，使用了 transmission rpc，我是比较喜欢里面的RSS文件大小过滤功能，太大太小的文件都不会下载，qb要写正则表达式很麻烦。
https://github.com/BiglySoftware/BiglyBT-plugin-xmwebui/blob/master/rpc-spec.txt

tixati 3.29 之后官方已经支持规则了，3.29之前也支持自定义屏蔽客户端和Peer ID https://www.cometbbs.com/t/94202/1

bigly bt也可以，规则要自己写

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
Support for QueryBus?

Current implementation of MessageBusSupportingMiddleware doesn't return result from handler.
Because of that it can't be used to create i.e. QueryBus.
Is there any reason for this design decision?
I know there was RFC already (#16), but it was closed.
There would be no BC break (as no return value means NULL right now).

@matthiasnoback the author of the SimpleBus Library's blogged about the reason to not return anything and the design of the package:

http://php-and-symfony.matthiasnoback.nl/2015/01/a-wave-of-command-buses/
http://php-and-symfony.matthiasnoback.nl/2015/01/responsibilities-of-the-command-bus/
http://php-and-symfony.matthiasnoback.nl/2015/01/from-commands-to-events/
http://php-and-symfony.matthiasnoback.nl/2015/01/some-questions-about-the-command-bus/
http://php-and-symfony.matthiasnoback.nl/2015/01/collecting-events-and-the-events-aware-command-bus/

The short version is that its intentional because a Command Handler is not ment to return anything and  by not allowing this in the full stack you really can't and you should really think about command's and what the are doing. There was an discussed about implementing a query bus in #16 with some interesting suggestions but it was closed. Another issue on the subject of returning something is #47.

AFAIK the package contains only universal message bus (which can be used as CommandBus, EventBus). I agree that command bus shouldn't return any result, but CommandBus != QueryBus as the purpose is different and "Command buses aren't supposed to do that" isn't the answer.
Many CQRS apps uses both command and query buses. Right now there is high duplicity necessary (= you have to implement query bus yourself or use different package).

Yes CommandBus != QueryBus but you question was 'Is there any reason for this design decision?' and there was thats what i tried to answer.
In #16 @matthiasnoback decided to close the QueryBus part to get a better view on how te solve the question. I think it's create to start a discussion about this again because we where thinking on implementing QueryBus. Our main goal is to be able to send query commands and allow an async response by using for example RabbitMQ RPC. Our main purpose for this is that we need to query a closed system and by using RabbitMQ on the outside we could use a QueryBus with RPC to call internal job's te return the result.

I see the problem. But in most cases queries are handled synchronously and for synchronous handling is return value best solution.

I agree we could stil use the return value if i implement the RPC method because it just waits until it's done. I don't want to query in async but use RabbitMQ as a communication method.

I'm not sure how often an actual query bus will make sense. When you need data/an object you ask a repository for it, and then you could implement the repository as a so-called facade, which behind-the-scenes actually does some RPC call.
I've come to think that the nature of a query bus is quite different as well. Both the command bus and the event bus can queue messages in-memory, then handle them one after another. See https://github.com/SimpleBus/MessageBus/blob/master/src/Bus/Middleware/FinishesHandlingMessageBeforeHandlingNext.php#L34. Supporting a return value in this example would be impossible since in fact there could be/are multiple return values.
Of course, you're free to implement a query bus. And it might be a nice package too. If any of you would like to work on it, I'd be happy to host it even at the SimpleBus organization. It should be really simple, but you can't use a lot from this library, except for the callable resolver stuff.

Hmm interesting the RPC inside the repository I had not thought of great idea tnx!

@matthiasnoback I agree that FinishesHandlingMessageBeforeHandlingNext doesn't make sense when it comes to queries. I don't see problem with returning NULL in that middleware. It will never be used in query handler, and support for return value for command handlers isn't desirable.
I was thinking about separate package, but it would contain only copy/paste from MessageBusSupportingMiddleware with two returns keyword.

@fmasa Right, totally get it. My point being, we can't just add those return statements in this package because it would be incompatible with the command bus/event bus (because of that FinishesHandlingMessageBeforeHandlingNext middleware - which return value will become the return value?). Besides, I feel that having no return value has so far actually been of great value in the "secret" purpose of pushing developers to learn CQRS :)

Just an idea: wouldn't it be possible to give the Query Bus an object that it should write its data to? That way it doesn't need to return anything.

@MidnightDesign It's perfectly possible to "hack" it that way. But I still find it rather ugly. I'd like to have first-class support for query bus.
I partially agree with @matthiasnoback (point About forcing devs to learn about CQRS :) ), that it should be in separate package. The only thing I'm thinking about is how to avoid (small) duplicity of callable resolver.

Introducing a return value is in fact a BC break, since existing middlewares would have to return the value returned by $next(). This is why I don't want to introduce this change in the main package. If you want to do it, just create a new package (it can be an official SimpleBus package). And make it depend on the MessageBus package so you can reuse the callable/resolver stuff :)

I've implemented a POC for a QueryBus based on the @MidnightDesign idea. You can review it at https://github.com/ajgarlag/AjglSimpleBusQueryBus

Hello, i've created a bundle for Symfony 2.x/3.x based on @ajgarlag implementation of QueryBus.
You can check it out here: warezgibzzz/QueryBusBundle

I'm closing this issue for me to be able to keep an eye on what has to be done ;) Thanks for discussing this and offering your alternatives!

authors: MidnightDesign ajgarlag cmodijk fmasa matthiasnoback warezgibzzz

repo: SimpleBus/MessageBus

license: mit

license_source: bigquery


text:
Change transition style

Thanks for this repo. Great job. How do we change page transition style ? I need a fade effect in my project

Hey @madeInLagny , Nice to hear you're enjoying the repo.
I'll see into the ease of implementing a few different transition styles and allowing users to define their own ones.
I'll update here on the progress today

Hey, @madeInLagny .
I've implemented custom transition, and it's released with the 5.6.0 patch to the package.
For docs, you can go to https://router.matsu.fi/recipes/transition-styling
and for an example you can see that codesandbox

authors: Matsuuu madeInLagny

repo: Simplr/simplr-router


text:
Shift register with millis funtion

i want to use millis funtions on shift register outputs, im used sensors to tigger  lights but as im usig delay to turn on lights one by one. which makes the other sensor trigger useless...and this is sensitive to my project because it has people count . soo sensors has to work all time .
soo how to use millis in shift register output pins

i want to use millis funtions on shift register outputs, im used sensors to tigger lights but as im usig delay to turn on lights one by one. which makes the other sensor trigger useless...and this is sensitive to my project because it has people count . soo sensors has to work all time .
soo how to use millis in shift register output pins

Hi @itsboo07 ... why don't you post your code and we will try to help you with eliminating delays from your code. This issue isn't really related to this project, as delays are not used within this code base ... but I'll help you figure it out ... but I'll need a little more info to make that happen 😄

sorry for posting here.
Im making a project of automatic stair case light with people count using 4 ir sensors and have used shift register to take the outputs.
the real problem i face is...i have set code in such a what that lights turn one other  one and goes off one other one. and have used delays for that...as my main motive of this project is about counting people in and out to trigger the funtions
real probelm is..when  one ir sensor is triggers and lights start to turn one by one.  and becuse of use delays . count funtions dont work  untill that funtion is comleted which makes a flaw .
it would be really great if you help me as im new to all this and was real hard time building this whole code soo far.
code:
`#include <ShiftRegister74HC595.h>
// create a global shift register object
// parameters:  (data pin, clock pin, latch pin)
ShiftRegister74HC595<2> sr(14, 16, 15);
#define sensorPin1 5        //ir sensor 1
#define sensorPin2 7        //ir sensor 2
#define sensorPin3 9        //ir sensor 3
#define sensorPin4 11       //ir sensor 4
int sensorState1 = 0;
int sensorState2 = 0;
int sensorState3 = 0;
int sensorState4 = 0;
int count=0;
int time1=200;
void toupon() {                  //Turn on 1st to last light
for(int i=0;i<16;i++) {
sr.set(i, HIGH);
delay(time1);
Serial.print("turn on light");
Serial.println(i);
}
}
void toupoff() {                  //Turn off from 1st to last light
for(int i=0;i<16;i++) {
sr.set(i, LOW);
delay(time1);
Serial.print("turn off light ");
Serial.println(i);
}
}
void todownon() {                 //turn on last to first light
for(int i = 15; i>=0; i--) {
sr.set(i, HIGH);
delay(time1);
Serial.print("turn on light ");
Serial.println(i);
}
}
void todownoff() {                //turn off last to first light
for(int i = 15; i>=0; i--) {
sr.set(i, LOW);
delay(time1);
Serial.print("turn off light ");
Serial.println(i);
}
}
void setup()
{
Serial.begin(9600);
Serial.println("FUN Started");
Serial.print(count);
pinMode (sensorPin1,INPUT);
pinMode (sensorPin2, INPUT);
pinMode (sensorPin3,INPUT);
pinMode (sensorPin4,INPUT);
}
void loop() {
int timex=800;
sensorState1 = digitalRead(sensorPin1);
sensorState2 = digitalRead(sensorPin2);
sensorState3 = digitalRead(sensorPin3);
sensorState4 = digitalRead(sensorPin4);
int lower = digitalRead(sensorPin1);
int upper = digitalRead(sensorPin4);
if (count < 0)
{
count = 0;
}
if(sensorState1 == LOW || sensorState4 == LOW ){   //counts people IN
count++;
Serial.println(count);
delay(timex);
}
if(sensorState2 == LOW || sensorState3 == LOW ){   //counts people OUT
count--;
Serial.println(count);
delay(timex);
}
if(count==0 && sensorState2 == LOW)
{
todownoff();
}
if(count==0 && sensorState3 == LOW)
{
toupoff();
}
if (count==1  &&  sensorState1 == LOW)
{
toupon();
}
if (count==1 &&  sensorState4 == LOW)
{
todownon();
}
}
`

OK, I may have over thunk this but I wanted to stay to exactly what you had ...
#include <ShiftRegister74HC595.h>

// create a global shift register object
// parameters: <number of shift registers> (data pin, clock pin, latch pin)

ShiftRegister74HC595<2> sr(14, 16, 15);

#define sensorPin1 5  // ir sensor 1
#define sensorPin2 7  // ir sensor 2
#define sensorPin3 9  // ir sensor 3
#define sensorPin4 11 // ir sensor 4

int sensorState1 = 0;
int sensorState2 = 0;
int sensorState3 = 0;
int sensorState4 = 0;

int count = 0;   // current counter count

int time1 = 200; // delay between shiftregister updates
int timex = 800; // delay between counter updates

unsigned long previousMode;    // Previous Millis for mode timer
unsigned long previousCount;   // Previous Millis for counter timer (delay between counts)
int           current = 0;     // current shiftregister
int           mode = 0;        // current mode
bool          active = false;  // is mode active ?

void toupon() {  // Turn on 1st to last light
  sr.set(current, HIGH);
  Serial.print("turn on light");
  Serial.println(current);
  current++;
  if(current > 15) {
    current = 0;
    active = false; // mode finished
  }
}

void toupoff() {  // Turn off from 1st to last light
  sr.set(current, LOW);
  Serial.print("turn off light ");
  Serial.println(current);
  current++;
  if(current > 15) {
    current = 0;
    active = false; // mode finished
  }
}

void todownon() {  // turn on last to first light
  sr.set(current, HIGH);
  Serial.print("turn on light ");
  Serial.println(current);
  current--;
  if(current < 0) {
    current = 15;
    active = false; // mode finished
  }
}

void todownoff() {  // turn off last to first light
  sr.set(current, LOW);
  Serial.print("turn off light ");
  Serial.println(current);
  current--;
  if(current < 0) {
    current = 15;
    active = false; // mode finished
  }
}

void setup() {
  Serial.begin(9600);
  Serial.println("FUN Started");

  pinMode(sensorPin1, INPUT);
  pinMode(sensorPin2, INPUT);
  pinMode(sensorPin3, INPUT);
  pinMode(sensorPin4, INPUT);

  previousMode = millis();  // init previousMode timer
  previousCount = millis(); // init previousCount timer
}

void loop() {
  unsigned long currentMillis = millis(); // get current Millis for this frame

  sensorState1 = digitalRead(sensorPin1);
  sensorState2 = digitalRead(sensorPin2);
  sensorState3 = digitalRead(sensorPin3);
  sensorState4 = digitalRead(sensorPin4);

  if((currentMillis - previousCount) >= timex) { // delay between taking a reading
    previousCount = currentMillis;
    if(sensorState1 == LOW || sensorState4 == LOW ) {  // counts people IN
      count++;
      Serial.println(count);
    }
    if(sensorState2 == LOW || sensorState3 == LOW ) {  // counts people OUT
      count--;
      if(count < 0) { // bottom out counter count to zero
        count = 0;
      }
      Serial.println(count);
    }
    if(count == 0 && sensorState2 == LOW) {
      mode = 0;
      active = true;
    }
    if(count == 0 && sensorState3 == LOW) {
      mode = 1;
      active = true;
    }
    if(count == 1 && sensorState1 == LOW) {
      mode = 2;
      active = true;
    }
    if(count == 1 && sensorState4 == LOW) {
      mode = 3;
      active = true;
    }
  }

  if(active) {
    if((currentMillis - previousMode) >= time1) { // delay between sr updates
      previousMode = currentMillis;
      switch (mode) {
        case 0:
            todownoff();
        break;
        case 1:
            toupoff();
        break;
        case 2:
            toupon();
        break;
        case 3:
            todownon();
        break;
      }
    }
  }
}

hope that helped ... although I can see a problem when the counter switches between in and out it will screw up the mode mid processing and probably not giving you the expected results ...

thanks for your time , but this code isnt funtioning.
its not turnings the lights on or off not sure whats wrong here

what do you get at the serial console ... does it recognize the changes at the sensors?

yes but not exactly
the issues are
light turn on counts are runnning in loop and going just going all way from 16 ,17,18to 100...110..etc
and when sensor 4 or 3 are triggered its not working that way
and somtimes sensors are triggered funtions take some delay to start and also most of the time lights animiations are either going wrong or just not working
here is the video link on how my code performes
https://photos.app.goo.gl/Wjpon4ukS9M82Pqg8

I made a change to the file above to initialize the current position ... can you see if that makes any difference? ... the problem also maybe the way timex is being applied ...

hi...i would say the last code was better then this updated one.
before the code was updated. sensor 1 , 2 and 3 was working fine in last code
only sensor 4 was funtioning as same as sensor 3
also when sensor 1 and 2 are triggered together it goes to end less loop
the recent code has issues ..sensor 1 is just turning on the 15th light alone and isnt performing .
i would say code before updated works better then the last one

is it possible for you to come in discord soo i can share my screen and you can watch the serial monitor yourself ?that could really be helpful .

last try ... I left the delays in that were used during the sensor reading ... this will block the lights ... but is closer to your original code ...
#include <ShiftRegister74HC595.h>

// create a global shift register object
// parameters: <number of shift registers> (data pin, clock pin, latch pin)

ShiftRegister74HC595<2> sr(14, 16, 15);

#define sensorPin1 5  // ir sensor 1
#define sensorPin2 7  // ir sensor 2
#define sensorPin3 9  // ir sensor 3
#define sensorPin4 11 // ir sensor 4

int sensorState1 = 0;
int sensorState2 = 0;
int sensorState3 = 0;
int sensorState4 = 0;

int count = 0;   // current counter count

int time1 = 200; // delay between shiftregister updates
int timex = 800; // delay between counter updates

unsigned long previousMode;    // Previous Millis for mode timer
unsigned long previousCount;   // Previous Millis for counter timer (delay between counts)
int           current = 0;     // current shiftregister
int           mode = 0;        // current mode
bool          active = false;  // is mode active ?

void toupon() {  // Turn on 1st to last light
  sr.set(current, HIGH);
  Serial.print("turn on light");
  Serial.println(current);
  current++;
  if(current > 15) {
    current = 0;
    active = false; // mode finished
  }
}

void toupoff() {  // Turn off from 1st to last light
  sr.set(current, LOW);
  Serial.print("turn off light ");
  Serial.println(current);
  current++;
  if(current > 15) {
    current = 0;
    active = false; // mode finished
  }
}

void todownon() {  // turn on last to first light
  sr.set(current, HIGH);
  Serial.print("turn on light ");
  Serial.println(current);
  current--;
  if(current < 0) {
    current = 15;
    active = false; // mode finished
  }
}

void todownoff() {  // turn off last to first light
  sr.set(current, LOW);
  Serial.print("turn off light ");
  Serial.println(current);
  current--;
  if(current < 0) {
    current = 15;
    active = false; // mode finished
  }
}

void setup() {
  Serial.begin(9600);
  Serial.println("FUN Started");

  pinMode(sensorPin1, INPUT);
  pinMode(sensorPin2, INPUT);
  pinMode(sensorPin3, INPUT);
  pinMode(sensorPin4, INPUT);

  previousMode = millis();  // init previousMode timer
  previousCount = millis(); // init previousCount timer
}

void loop() {
  unsigned long currentMillis = millis(); // get current Millis for this frame

  sensorState1 = digitalRead(sensorPin1);
  sensorState2 = digitalRead(sensorPin2);
  sensorState3 = digitalRead(sensorPin3);
  sensorState4 = digitalRead(sensorPin4);

  if(active) {
    if((currentMillis - previousMode) >= time1) { // delay between sr updates
      previousMode = currentMillis;
      switch (mode) {
        case 0:
            todownoff();
        break;
        case 1:
            toupoff();
        break;
        case 2:
            toupon();
        break;
        case 3:
            todownon();
        break;
      }
    }
  }

  if(sensorState1 == LOW || sensorState4 == LOW ) {  // counts people IN
    count++;
    Serial.println(count);
    delay(timex);
  }

  if(sensorState2 == LOW || sensorState3 == LOW ) {  // counts people OUT
    count--;
    if(count < 0) { // bottom out counter count to zero
      count = 0;
    }
    Serial.println(count);
    delay(timex);
  }

  if(count == 0 && sensorState2 == LOW) {
    mode = 0;
    current = 0;
    active = true;
  }

  if(count == 0 && sensorState3 == LOW) {
    mode = 1;
    current = 0;
    active = true;
  }

  if(count == 1 && sensorState1 == LOW) {
    mode = 2;
    current = 15;
    active = true;
  }

  if(count == 1 && sensorState4 == LOW) {
    mode = 3;
    current = 15;
    active = true;
  }
}

uh...same issue sfranzyshen
senssor 4 works senor 1, 2 , 3 isnt working the right way
if sensor 4 is triggered for like 2 time it just starts to count++ even its not triggered
it would be helpful if you seee the serial monitor yourself. i can share my screen in discord

can you tell me more about your sensors ... how do they behave ...

do they go HIGH or LOW when triggered
are they real-time response (do they have a delay or no delay when changing state)

When triggered SENSORS go LOW
Only sensor 4 works with trigger.. Yes it turned on lights one by one with some delay.

this is as close to your original code as I can get ... it doesn't address your original problem ... yet it should run exactly (blocking) as your code does ...
#include <ShiftRegister74HC595.h>

// create a global shift register object
// parameters: <number of shift registers> (data pin, clock pin, latch pin)

ShiftRegister74HC595<2> sr(14, 16, 15);

#define sensorPin1 5  // ir sensor 1
#define sensorPin2 7  // ir sensor 2
#define sensorPin3 9  // ir sensor 3
#define sensorPin4 11 // ir sensor 4

int sensorState1 = 0;
int sensorState2 = 0;
int sensorState3 = 0;
int sensorState4 = 0;

int count = 0;   // current counter count

int time1 = 200; // delay between shiftregister updates
int timex = 800; // delay between counter updates

unsigned long previousMode;    // Previous Millis for mode timer
unsigned long previousCount;   // Previous Millis for counter timer (delay between counts)
int           current = 0;     // current shiftregister
int           mode = 0;        // current mode
bool          active = false;  // is mode active ?

void toupon() {  // Turn on 1st to last light
  sr.set(current, HIGH);
  Serial.print("turn on light");
  Serial.println(current);
  current++;
  if(current > 15) {
    current = 0;
    active = false; // mode finished
  }
}

void toupoff() {  // Turn off from 1st to last light
  sr.set(current, LOW);
  Serial.print("turn off light ");
  Serial.println(current);
  current++;
  if(current > 15) {
    current = 0;
    active = false; // mode finished
  }
}

void todownon() {  // turn on last to first light
  sr.set(current, HIGH);
  Serial.print("turn on light ");
  Serial.println(current);
  current--;
  if(current < 0) {
    current = 15;
    active = false; // mode finished
  }
}

void todownoff() {  // turn off last to first light
  sr.set(current, LOW);
  Serial.print("turn off light ");
  Serial.println(current);
  current--;
  if(current < 0) {
    current = 15;
    active = false; // mode finished
  }
}

void setup() {
  Serial.begin(9600);
  Serial.println("FUN Started");

  pinMode(sensorPin1, INPUT);
  pinMode(sensorPin2, INPUT);
  pinMode(sensorPin3, INPUT);
  pinMode(sensorPin4, INPUT);

  previousMode = millis();  // init previousMode timer
  previousCount = millis(); // init previousCount timer
}

void loop() {
  unsigned long currentMillis = millis(); // get current Millis for this frame

  sensorState1 = digitalRead(sensorPin1);
  sensorState2 = digitalRead(sensorPin2);
  sensorState3 = digitalRead(sensorPin3);
  sensorState4 = digitalRead(sensorPin4);

  if(active) {
    if((currentMillis - previousMode) >= time1) { // delay between sr updates
      previousMode = currentMillis;
      switch (mode) {
        case 0:
            todownoff();
        break;
        case 1:
            toupoff();
        break;
        case 2:
            toupon();
        break;
        case 3:
            todownon();
        break;
      }
    }
    return;
  }

  if(sensorState1 == LOW || sensorState4 == LOW ) {  // counts people IN
    count++;
    Serial.println(count);
    delay(timex);
  }

  if(sensorState2 == LOW || sensorState3 == LOW ) {  // counts people OUT
    count--;
    if(count < 0) { // bottom out counter count to zero
      count = 0;
    }
    Serial.println(count);
    delay(timex);
  }

  if(count == 0 && sensorState2 == LOW) {
    mode = 0;
    current = 0;
    active = true;
  }

  if(count == 0 && sensorState3 == LOW) {
    mode = 1;
    current = 0;
    active = true;
  }

  if(count == 1 && sensorState1 == LOW) {
    mode = 2;
    current = 15;
    active = true;
  }

  if(count == 1 && sensorState4 == LOW) {
    mode = 3;
    current = 15;
    active = true;
  }
}

if that didn't work like your previous code did then I can only assume that your sensors have a reset timeout ... so when they get triggered ... they stay low for a period of time even if they are no longer getting triggered ...

hi...i tried out the last code
serial monitor shows,
when sensor 2 is activated: turn off light 0
when sensor 1 is activated: turn on light15
but sensor 3 and 4 is working fine.

hey thanks for your efforts on  my code. i really appreciate you
I made this working by doing this, which is almost same to your code
my working code
https://pastebin.com/iyrekAKe

in this code?
https://pastebin.com/wRJsLVPx
can you eliminate  delays in count part..?
as the counter is working all fine/


text:
EntityJs incompability

Mod Name
EntityJs
Mod Homepage
https://www.curseforge.com/minecraft/mc-mods/entityjs
Minecraft version
1.20.1
Describe the bug
You can't access server side values in places you normally can
Steps to reproduce
kubejs.zip
Install kubejs, entityJs and connector, together with all their dependencies
You don't even need to have any fabric mod
Put the folder from the zip into your .minecraft folder
Start the game
Spawn a kubejs:npc1
It basicly just is a blue cube, that jumps from time to time
If you uninstall connector and spawn another npc1, you will see that it basicly never jumps
This is the code that creates the entity:
StartupEvents.registry('entity_type', event => {
    event.create('npc1', 'entityjs:animal')
    .eggItem(item => {
        item.backgroundColor(0x0000FF)
        item.highlightColor(0x0099FF)
    })
    .onInteract(ctx => {
        if(ctx.hand == 'MAIN_HAND') {
            if(!ctx.entity.getLevel().isClientSide()) return InteractionResult.PASS
            Client.player.sendData('rpg_npc_interaction', {entity:ctx.entity.stringUuid,level:ctx.entity.level.dimension.toString()})
        }
        return InteractionResult.PASS
    })
    .isPersistenceRequired(true)
    .isImmobile(entity => {
        return true
    })
    .isInvulnerableTo(ctx => {
        if(ctx.damageSource.type().msgId() != 'genericKill') {
            return true
        } else {
            return false
        }
    })
    .isPushable(false)
    .addAnimationController('idleAnimation', 5, e => {
        e.addTriggerableAnimation('idle', 'idleing', 'play_once')
        return true
    })
    .tick(entity => {
        if (entity.age % 100 != 0) return
        if (Math.random() <= 0.99) return
        entity.triggerAnimation('idleAnimation', 'idleing')
    })
})

We mainly care about the tick methode here. As you can see I test if the age of the entity is devidable by 100 with 0 left. (The % operator returns the number that is left when dividing by a number) If not I return. Then I have a random factor, to only provide a verry small chance. If both of those don't return, I trigger the animation, in this case a little jump.
If everything works fine, this should basicly never trigger, because every 100 ticks there is a 1/100 chance.
So now to the problem: entity.age only exists on the server. But if sinytra connector is installed, it can't access the server for some reason. So it returns 0. 0/100 has 0 left, so the first check always succeeds. This is why it jumps pretty often with connector installed
Logs
https://gist.github.com/DragonMaster14545/2bf7dda10a040a13e9b7400cc337f47b
Additional context
Also I see this warning appear a lot in the log:
[03Mar2024 16:08:09.886] [Server thread/WARN] [net.minecraft.world.entity.ai.attributes.AttributeMap/]: Ignoring unknown attribute 'reach-entity-attributes:reach'
I already talked to the creator of entityJs, he said this is not on his side
It would be awesome if this could be fixed, because I love playing my pack with axiom
Thanks a lot in advance

Update on this, I just noticed this is a way bigger problem Im pretty sure
EntityJSEvents.addGoalSelectors('kubejs:npc1', e => {
    e.customGoal(
        'move_to_persistent_data_position',
        1,
        mob => {
            return true
        },
        mob => {
            return true
        },
        true,
        mob => {
                if(mob.persistentData.targetX && mob.persistentData.targetY && mob.persistentData.targetZ) {
                    mob.getNavigation().moveTo(mob.persistentData.targetX,mob.persistentData.targetY,mob.persistentData.targetZ, 1.0);
                }
        },
        mob => {
            mob.getNavigation().stop();
        },
        true,
        mob => {
                if(mob.persistentData.targetX && mob.persistentData.targetY && mob.persistentData.targetZ) {
                    mob.getNavigation().moveTo(mob.persistentData.targetX,mob.persistentData.targetY,mob.persistentData.targetZ, 1.0);
                }
        }
    );
})```This is a custom entity goal with entityJs, if the entity has persistent data (That is only on the server) it should move to  a specific position. But it seams like the persistent data is always empty here. This is also fixed when disabeling connector. This code is run on the server though, not on the client

I was able to trace this down to a bizarre scenario where changing the access level of AgeableMob#age to public triggers this issue. Connector applies a global access widener to all package-private and protected fields to prevent issues with package-level access between changing mappings.
https://github.com/Sinytra/Connector/blob/e40dcef57cf88ddb36bbcfdb43f4a341e1eea465/src/main/java/dev/su5ed/sinytra/connector/service/ConnectorPreLaunchPlugin.java#L44-L53
What makes things interesting, though, is that I was also able to trigger this with an ordinary access transformer file.
public net.minecraft.world.entity.AgeableMob age # age

As I was investigating this, I found out the AgeableMob#age field's value doesn't match the value returned by entity.age in the script, which seems to point to Entity#tickCount instead.
It turned out to be an alias set by kubejs. Normally, the protected field is hidden from outside access and doesn't get in the way of the aliased tickCount field. However, after being set to public, it now takes priority, hiding the value of tickCount (age).

So, is this something that you can fix?

Also, that doesn't explain why the server script code doesn't work

I tried running the server script, but it doesn't move the entity regardless of connector/FFAPI being installed.

You have to set in its persistent data where it should move to. Thats thw hole purpose of that code

With /kubejs persistent_data entity your entity merge {targetX:0, targetY:64, targetZ:0}
Just replace those coordinates with some near you. Also note, that this only works on the custom npc1 entity

I've tried that now, but the entity still doesn't move. The script also seems to be loaded correctly according to the server logs.

Try just console.logging the persistent data, with connector it will always be {}

For me the moving works fine, but Ive changed the code quite a bit since then

Forks fine for me both with and without connector

Thats weird

Im not at my computer right now so I cant test it

At which point does the persistent data become empty? Is it on world reload, game reload or immediately after setting it?
Don't feel rushed, I can get back to this anytime later.

The persistent data is there, the entityJs methode just doesn't seem to have acces to it. For the rest of my scripts its perfectly fine

So, I just tested it and it worked fine as well. Weird, sorry for annoying you with that then.

I talked to Lat about this on discord. Unfortunately, there is no way to get around the alias and directly access the field in KubeJS at the moment, sorry. Globally widening fields' access is necessary to prevent package-level conflicts usually doesn't have any side effects. Given that this can also be reproduced without Connector, I'll delegate it to the KubeJS devs to fix.

Thanks for trying thought

repo: Sinytra/Connector


text:
UI Improvements

Still many things to do:

[ ] allow more customization in the placement of Text for Check/RadioButtons
[ ] allow more customization in the placement of Title bar and Buttons for Windows
[x] implement gradient-based Skins as an alternative to the use of Textures and Pixmaps
[x] implement Comboboxes

Gradient and solid-color Appearances implemented.
Reworked the Skin system so that a single Appearance can contain a number of Skins of one or multiple types independent from each other.

repo: SirePi/duality-frozen


text:
🛑 Pixelfed is down

In e456f3e, Pixelfed (https://kvasir.lanofthedead.xyz) was down:

HTTP code: 502
Response time: 792 ms

Resolved: Pixelfed is back up in 352e2b0 after 7 minutes.

repo: SiskoUrso/literate-octo-waddle


text:
[Vue] Fix for bug in Link component child check

If the "children" function is defined it will always have a length of 0. This check needs to check the length of the output of the children function, instead of the length of the function.
Without this fix the template will always render the linkText before the children elements if they are present.

[x] This PR follows the Contribution Guide

Description / Motivation

The current render of:
<sc-link :field="linkItem.fields.Link">
    This tag should be the only thing in the a tag
</sc-link>

will show as:

    Text from the Sitecore Link Description field or the href
    This tag should be the only thing in the a tag

By applying this fix it will show as:

    This tag should be the only thing in the a tag

as expected.
Testing Details

[ ] Unit Test Added
[x] Manual Test/Other (Please elaborate)

Import Link as ScLink
Put a sc link element with child elements in a vue template and populate it with a Sitecore link.
Example:
<template>
...
<sc-link :field="linkItem.fields.Link">
    This tag should be the only thing in the a tag
</sc-link>
...
</template>

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

@OSOdevK  Thank you for your contribution!
I pulled your changes and added a bit more changes in #1570, so I close current PR

source: gharchive/pull-request

authors: OSOdevK illiakovalenko

repo: Sitecore/jss


text:
Fullscreen menus

All the menus for restarting the game, changing the settings and viewing highscores are implemented using the menus at the top of the screen (I guess it's called tool palette, but I'm not sure). What about full-screen graphical menus? Sounds like a nice enhancement, but I'm afraid that it's going to destroy the minimalist feeling...
However, I could imagine working on this feature.

That certainly would be very cool! If it has the same "look" as the rest of the UI/Game it would definitely look a lot better than the simple menus.
You could work on this feature on a new branch an make a PR at the end so I can check it out!
Thank you for putting so much work into this!

How are your UI/UX skills? Should I try to make a little mockup for the interface?

I don't have very much experience so it would be nice if you have the time to.

I've thought about the game structure before starting to code and this is what I've come up with:

Looks pretty good! The only thing I'd change is having the "Back to Main Menu" in the Pause Screen.
So in the running game you press ESC -> Pause Menu with

Resume
Settings
Help
Restart (with confirmation)
Exit to Main Menu (or just "Exit") (with confirmation)

The Main Menu could also have a "Help" option.
Btw, I found this yesterday: https://tcrf.net/Proto:Minesweeper_(Windows,_1990)/Mine_2.9
It shows some images from the Original Game Prototype, with a settings menu.
I will probably base the mockups on the design they had back then with the buttons and so on.
Not sure if I have the time for it today tho.

Another thing which could be nice is some kind of key remapping. So you can set your own buttons for moving the cursor, setting flags, etc.
Also I thought about some simple localization using the Locale API from TI Nspire. This would only require a table with  the translated strings for each language. I could provide a German translation for the game and it would just fallback to English if the user's language doesn't exist.
And don't worry I definitely want to help you with some features! I just hope my Lua knowledge is still up-to-date haha
I'll start with the mockups later today.

Maybe you've already done it but if you are interested you can download the original minesweeper from here and reverse engineer/compare the behavior and stuff.
I recently noticed that the smiley doesn't have the "scared" state while clicking on a tile

In my opinion, these ideas are very nice and I enjoy tinkering with Lua so far, although I don't move forward very fast.

repo: Skayo/TI-Nspire-Minesweeper


text:
FAI-2141 Added the new attributes OtherAddresses & IsPrimaryLocation to Azure Search Document

Story: https://skillsfundingagency.atlassian.net/browse/FAI-2141

Changed to target main


text:
fix: tasks reloading

Tasks are not reloadable right now. This PR fixes that.

Leave this on hold, im not sure how i feel about this atm

Leave this on hold, im not sure how i feel about this atm


text:
npm start: updating

npm start should look at process.env.NODE_ENV.
if NODE_ENV != 'production:
  start node webpack dev server
  start client webpack dev server
  start built node code
else:
  start prebuilt node code

this works differently on a push deploy platform like heroku where it builds and runs in production

authors: iamdustan jcgertig

repo: Skookum/generator-genreact


text:
Fix print message error

as title

Thanks for your contribution

authors: ascrutae zouyx

repo: SkyAPM/SkyAPM-nodejs


text:
Add Golang Runtime Metrics e2e test

[ ] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
[ ] Update the CHANGES log.

Add golang runtime metrics e2e test

Codecov Report

Merging #172 (cf30e2b) into master (cbdde90) will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #172      +/-   ##
==========================================
- Coverage   61.88%   61.85%   -0.04%
==========================================
  Files          23       23
  Lines        1220     1219       -1
==========================================
- Hits          755      754       -1
  Misses        405      405
  Partials       60       60

Impacted Files
Coverage Δ

reporter/grpc.go
51.20% <ø> (-0.17%)
:arrow_down:

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

authors: codecov-commenter easonyipj


text:
Fix Jerry talismans

Didn't notice that for some reason it doesn't include the missing talis into the total (it's still 64/64), will check

Didn't notice that for some reason it doesn't include the missing talis into the total (it's still 64/64), will check

repo: SkyCryptWebsite/SkyCrypt


text:
small fix

k love u bye

Lol thanks, but I was just about to commit that. If you make commits in the future though please make sure the commit message is more descriptive.

repo: Skylumz/Sollumz


text:
normal_ext base material gets wrong lighting

I did remark on this before that normal_ext materials were somewhat dark but only now it occurred to me that there is a mismatch with how the material gets lit. From the looks of it, I want to say it's not receiving all the lights, I think. In the screenshot there is a normal_ext.specular material to contrast it, as the specular extension does get lit as it should as far as diffuse is concerned.
However, I need to question the specular reflection itself here; it's rather limited to one face of the pillar as if it was being calculated per vertex. The stock specular interacts with the polygons much better, I want to say per pixel but my terminology might be misled here. But then, this could also be related to #55 because I am seeing a lot of polygon seams bleeding in this map and they sometimes bleed through a color so bright that it spikes the bloom. It's hard to tell what's going on at this point.

Just so I have a better grasp on what's going on, does this happen with normal_ext.specular.dynamic as the rendertype?

I'm not sure which one you mean? Also I'll take back that second point about the specular, it's the same as the stock specular so it's just what it is. I think the geometry itself would need to be redone better for the specular effect to look more natural.
But no, the color issue doesn't happen on any kind of specular extensions whatsoever. The specular mapped materials are correct, it's the regular normal_ext materials that have gone daffy. I did check if it might be because the normal maps between these materials use a different compression, but it doesn't seem to be the case.

Sorry, I was being hasty earlier and I think I misread what you were saying. (I thought the issue may have been to do with the normal mapping, but I realize now I was way off.)
Okay so the problem actually is (as opposed to whatever nonsense I was thinking it was) that normal_ext materials without specular lighting are darker than they should be yeah?
After checking out the responsible shader it looks like the diffuse texture is getting multiplied over the ambient and static lighting twice. Which in some cases will significantly decrease the amount brightness of the "reflected" light. It'll be an easy fix.
Do you think this could explain the problems you've been seeing?

Yeah that sounds like the root of it.

authors: DoctorAnsem SleepKiller

repo: SleepKiller/shaderpatch


text:
Clarification in the documentation about generated logs

The documentation https://docs.tamemycerts.com/#logs states:
"Events 1 and 11 occur only if the certification authoritys LogLevel setting is configured to 4 (CERTLOG_VERBOSE) or higher." needs to be updated as well.
As far as I can see this applies to event ID 7 as well, which has log level Verbose.

Thank you, I'll fix this in the docs.


text:
Compatibility

Compatibility with bc2
I can not put item conduits in the bc2 quarry would be better if it had compatability with the mod.

I cannot really see this being a thing because of how the bc2 quarry works. (assuming Buildcraft 2)
The way that the bc2 quarry works is that it pushes the mined items to an adjacent inventory as the quarry itself does not have a internal inventory. This is why this doesn't work with conduits as the conduits do not really have an inventory. The simple solution would be to just put a chest down next to the quarry and extract from the chest instead of from the quarry.
I am not sure what type of compatibility you are looking for with this.

I fixed ,can close if want

you can close it yourself, right beside the comment button

wow!

authors: Aiidoneus GhostShot3 mindforger

repo: SleepyTrousers/EnderIO

license: Unlicense


text:
Cannot place conduit facades in 1.12

Issue Description:
Note: If this bug occurs in a modpack, please report this to the modpack author. Otherwise, delete this line and add your description here. If you are using an unreleased version of Ender IO (e.g. for 1.8.9), please don't open an issue for features that have not been announced as "finished" or "working".
What happens:
Conduit facades cannot be placed over existing conduits via right-click. It just ignores the right click.
What you expected to happen:
Conduit facade should be placed in the specified location hiding that portion of the conduit.
Steps to reproduce:

Place a conduit
Right click a facade to try to hide that block's portion of the conduit.

...

Affected Versions (Do not use "latest"):

EnderIO: 1.12.2-5.0.22
EnderCore: 1.12.2-0.5.20
Minecraft: 1.12.2
Forge: 1.12.2-14.23.3.2673

Your most recent log file where the issue was present:
None.
Mods loaded:
EnderCore-1.12.2-0.5.20
EnderIO-1.12.2-5.0.22
hud-1.3.9-1.12
InventoryTweaks-1.63
jei_1.12.2-4.8.5.159
journeymap-1.12.2-5.5.2
LLOverlayReloaded-1.1.4-mc1.12
LunatriusCore-1.12.2-1.2.0.42-universal
MCMultiPart-2.5.0
MoreCommands-1.12.2-6.0
MouseTweaks-2.8-mc1.12.1
QuickLeafDecay-MC1.12.1-1.2.4
VeinMiner-1.12-0.38.2.647+b31535a
WailaHarvestability-mc1.12-1.1.12
Wawla-1.12.2-2.5.246
[pastebin/gist/etc link here]
Example: cannot place a facade to cover the turn in this image (or any conduits for that matter):
https://pasteboard.co/Hiq4ZIH.png

Conduit facades must be painted before they can be placed

I found out what my problem was... silly me. I was clicking a block that I wanted the facade to be placed next to, like when you place stairs. Now I see that I need to click the conduit NODE that will be wrapped by the facade. Not a bug after all, just me forgetting how to use Endio IO!

No worries

The code for this is still there, but it seems to not work...

authors: Astewen EpicSquid HenryLoenwind tyler489


text:
[5.0.26] Strange Interaction with Rotten Flesh, Thaumcraft, Natura

Issue Description:
Rotten Flesh fails to have any thaumcraft aspects.
What happens:
^
What you expected to happen:
Rotten Flesh having aspects (namely Humanus, Victus, Perditio)
Steps to reproduce:

Install the following modset:
Baubles [1.5.2]
EnderCore [0.5.30]
EnderIO [5.0.26]
Mantle [1.3.2.24]
Natura [4.3.2.49]
Thaumcraft [6.1.BETA16]
Forge [14.23.4.2707]
Hold shift while mouse is over Rotten Flesh in inventory

Affected Versions:

EnderIO: 5.0.26
EnderCore: 0.5.30
Minecraft: 1.12.2
Forge: 14.23.4.2707

Your most recent log file where the issue was present:
https://gist.github.com/Plet53/af00c40809b5d825ea137f1b8964a172

This doesn't sound like an Ender IO issue at all. Can you replicate it without ender io?

That's the screwed up part.
I can't

Coal and snowballs also don't have aspects with the .26 and .25 versions
The .24 version has them

Yes, the issue was around before then

This issue isn't resolved with the 5.0.29 version of EnderIO. Is it possible to turn this off with a config option or something?

This issue is present in my game (has EnderIO 5.0.26 and EnderCore 0.5.31 with Forge 14.23.4.2705 and MC 1.12.2), though I did not know it was a bug until now.

https://github.com/SleepyTrousers/EnderIO/blob/540cd7dae3dbcf4ed55f43e12c22bdcdd1035280/enderio-base/src/main/java/crazypants/enderio/base/integration/thaumcraft/ThaumcraftAspects.java#L26
I changed .add(getAspects(Items.COAL)) to .add(Aspect.FIRE, 10).add(Aspect.ENERGY, 10) and the normal coal got its aspects back, is getAspects buggy somehow when used like this?

Yeah im going to go report that....

@tyler489 Did you file a bug with azanor's github?
I just commented out the entire method loadAspects and things went back to normal. I know it's not a great fix, but Thaumcraft integration that breaks Thaumcraft isn't very useful to me. I was using an older EnderIO build, but it didn't have the refined storage conduits.
I don't know what part of the subrouting is breaking aspects on snow, because nothing references snow in that section that I noticed.
It would be great if you just removed the aspect integration in the next EnderIO release to fix Thaumcraft until the real problem is fixed.
Thanks.

https://github.com/SleepyTrousers/EnderIO/pull/4781
I submitted a pull request to remove the loadAspects function which restores the aspects that were lost with EnderIO integration. Hopefully the actual problem will be resolved and this won't be necessary, but it's an okay "right now" fix.

You can also readd the lost aspects using ModTweaker. Here is a demo ZenScript that readds Coal and Coal block aspects. It was tested with EnderIO 5.0.29 and EnderCore 5.35.
import thaumcraft.aspect.CTAspectStack;
readd aspects that EnderIO integration breaks
minecraft:coal.setAspects(aspect:ignis*10, aspect:potentia*10);
minecraft:coal_block.setAspects(aspect:ignis*67, aspect:potentia*67);

What makes you think this will ever be fixed, jd? I'm inclined to just completely remove Thaumcraft support for good...

It may not be, but TC is still in beta. A public beta, but still a beta. It's not even complete, so the term beta is a rather charitable one.
If maintaining the TC support code is problematic, I would drop it. You guys are doing amazing work for free, and I very much appreciate it.

Finally heard back from anazor.... 13 days later
https://gyazo.com/738a469b6002d4d9139194c517191b44

Even if there is no good way to know if his code has been run and calculated aspects already before the Ender IO code runs, why should calling his library functions break aspects on other items later? His response doesn't fully address the problem I think.

In init, as the Thaumcraft API states to use it "once Thaumcraft is past the FMLPreInitializationEvent phase". But moving that to after postInit should not be too hard. Sad that it took 2 months to get that tiny bit of information...

As of Beta 20 there's a new event for aspect registration and anything done before Thaumcraft's registration is cleared.

Yes i reported this on the discord already.

This is still a current problem even with Thaumcraft Beta 23 and Natura. Strangely enough, it does not happen if you remove Natura. I hope we can see an update to the Thaumcraft API soon.

Mario, Thaimcraft API changes won't help here, the most they can do is crash the game when Natura is installed. This needs a change in Natura, they need to register their aspects in post init instead of pre init as the old Thaumcraft API documentation claimed. Might be worth telling them (hint, hint)...

Yes but from what I can tell, I could not find any Thaumcraft integration code in Natura at all. I'm not sure if I missed it or not, but the issue does not persist if Ender IO is removed as well. It only happens if both are running. I'm only bringing this up here because of the weird nature of this, that it specifically needs both mods - not one or the other.

what version of enderio are u using as enderio fixed this already?

Quite sure this has nothing to do with Ender IO---we don't use Items.ROTTEN_FLESH at all in the Thaumcraft aspect code.
My guess is that there's a third mod in there that has a dependency on Ender IO, Natura, mantle, and/or Tinkers. When you add both Natura and Ender IO, the loading order gets shifted so that mod is loaded before Thaumcraft---triggering the error.

I do not have this issue in my own pack and I don't have Natura in there. Ender IO currently has no aspects but that's because thaumcraft changed to using an event for the aspect implementation.

Thaumcraft did change the API back around Aug 3rd to use an event for registration, and it does not look like Ender IO has updated the Thaumcraft API for about 4 months according to the repository. I have already tested all of this in an instance with only Natura, Ender IO, Thaumcraft and JEI - plus all core mods needed. Its not anything else, its certainly isolated to one of these mods. Thaumcraft calculates some aspects through recipes and the like, so that might be how it gets down to Rotten Flesh.

Like epic said thaumcraft made everything happen in an event  and enderio doesn't  use that event yet.. therefor  it  can not be enderio breaking it.

I can't explain why he doesn't get aspects, but that is irrelevant. The old methods to register aspects still work, they are only deprecated and will be removed in the future. They still fully work right now, and I can confirm that Ender IO has aspects on all of its alloys minus End Steel plus the other things it adds aspects to, like the tormented Enderman head.

see also https://github.com/Azanor/thaumcraft-beta/issues/1619


text:
bug: origin point on 2024 field image is off

I'm on MacOS x86, both with the official release build and a local version. I think it's a Mac only (eg. Safari webkit) issue because the (windows? not mac for sure) image in the CD post (duplicated below) is fine

I can confirm it happens on ARM64 and Rosetta 2

it seems to be the image that's off, because the lines are still at 0,0

i found a fix, working on the PR rn

Closed by #246

repo: SleipnirGroup/Choreo


text:
gui: Volume slider for feedback sound

Definitely missing a volume slider.
I found mids on distortion at the start quite overbearing, but maybe this is just a me issue.

IMO without the space it blends with the numbers too much, making it hard to read.

Okay, I hate it, but I hate UI inconsistencies more.

repo: SlimeVR/SlimeVR-Server


text:
Examples: Pharo support

Make an example app with a SmallJS browser front-end and a Pharo back-end.
Communication will be done through regular web API calls,
so no framework expansions will be needed on either side.
And the Pharo side, something like Seaside will have to be preloaded.
.
It will just be a showcase that gives existing Pharo developers a quick start option,
if they want to consider using SmallJS as a native front-end,
as an alternative to using bridgeing functionality, e.g. PharoJS.

Awesome idea.  Just what I'm looking for.
I'm working on a Pharo model of a Study Bible and want to front end it with web apps written by my budding web programmers.     I want to prototype the front end in ST to interact with the actual data model back end in Pharo.  Then have the students write various frontends using their usual HTML, CSS, JS tools and knowledge.

Great to hear, Michael, it would indeed be ideal for (starting) web developers
get starting expericience with Smalltalk.
Cheers, Richard

It's done :-)

authors: FunctionPoint MichaelKentBurns

repo: Small-JS/SmallJS


text:
🛑 My blog(github.io) is down

In feb1c55, My blog(github.io) (https://smartbrave.github.io/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: My blog(github.io) is back up in b17d879.

repo: SmartBrave/uptime


text:
🛑 My blog(CDN) is down

In 77fead1, My blog(CDN) (https://sbrave.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: My blog(CDN) is back up in 5ef05f0.


text:
🛑 My blog(github.io) is down

In c8a6f86, My blog(github.io) (https://smartbrave.github.io/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: My blog(github.io) is back up in e51107d.


text:
random_seed parameter is not working properly

Dear PyKEEN development group,
The setting of a seed on utilities/train_utils.py is after the model is initialized. The model is initialized in line 81 in utilities/pipeline.py, before the call to the method in utilities/train_utils in line 88. I suggest setting the seed before it so that it is applied to the model creation. I suggest this patch to fix the issue:
seed_fix.txt
Best wishes,

Please check this zip file with a modified version of a notebook with and without the patch. Comparison.zip

Hi @labrax,
thanks a lot. Can you please create a pull request?

@mali-git , it is submitted.

Thanks @labrax :)

authors: cthoyt labrax mali-git

repo: SmartDataAnalytics/PyKEEN


text:
Keen Vent

Only one model vent is supported. Please add the rest of the models to the library.

SV01-610-MP-1.0
SV02-610-MP-1.0
SV02-610-MP-1.1
SV01-410-MP-1.0
SV02-410-MP-1.0
SV01-410-MP-1.1
SV02-410-MP-1.1
SV01-410-MP-1.2
SV02-410-MP-1.2
SV01-410-MP-1.3
SV02-410-MP-1.3
SV01-410-MP-1.4
SV02-410-MP-1.4
SV01-410-MP-1.5
SV02-410-MP-1.5

authors: LionMike brianmsailing


text:
🛑 MPC Homepage is down

In 1d0481f, MPC Homepage (https://www.minorplanetcenter.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MPC Homepage is back up in bf5a963 after 8 minutes.

repo: Smithsonian/upptime


text:
🛑 MPC Homepage is down

In 40810c3, MPC Homepage (https://www.minorplanetcenter.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MPC Homepage is back up in efb0905 after 5 minutes.


text:
add: more velo tokens

Please review the following token assets:
📑 Description

Token Name: velo lp tokens
Project Website: https://yearn.finance
Explorer URI:

✅ Checks

[x] I created a new folder with the token address, all in lowercase
[x] I added the token's logo as a 32x32 PNG file, named logo-32.png
[x] I added the token's logo as a 128x128 PNG file, named logo-128.png
[x] I added the token's logo as a SVG file, named logo.svg
[x] All the tests have passed

Kek, soz @0xBasically I think I rushed this one :see_no_evil:

repo: SmolDapp/tokenAssets


text:
Переименовать setSSFlag в setSnakeskinFlag

Сабж

Решил переименовать просто в set.

Сделано.

repo: SnakeskinTpl/Snakeskin


text:
Fix windows dll gradle build

Changes proposed in this pull request
While trying to do a windows gradle build on my newly configured laptop (OS/libraries/SDKs/Visual Studio) there were the following three errors:

Include winsock2.h not found.
Include file winapifamily.h not found.
Link library file odbccp32.lib not found.

This was despite installing everything under the sun on my fresh windows VM, so finally concluded that this change was necessary to fix the build.
Patch testing
Fresh gradle build passed after this change.
ReleaseNotes changes
N/A
Other PRs
https://github.com/SnappyDataInc/snappy-odbc/pull/2 depends on this change.

On a related note, does the native client build work on your elementary OS installation? Perhaps you have to add the "linuxFlavour" for it in native/build.gradle.

@sumwale I haven't yet gotten around to building on linux, I am mainly looking to make some fixes to the MSI for branding and maybe authenticode signing, but yes, I saw that linuxFlavour checks for redhat/centos/mint, so if needed I'll create a PR(s) for that too, thanks!

@vjr please also delete branches after merge to avoid their explosion

authors: sumwale vjr

repo: SnappyDataInc/snappy-store


text:
Does komf update chapter covers?

I managed to get komf to update the metadata, but chapter covers are still the same - is this within the scope of komf?

I'm a bit overwhelmed by the setup; I'm not sure how I am even supposed to check if something broke or where I can see what features Komf supports/doesn't support.

At the moment Komf can only detect volumes and not chapters
Take for example bookwalker series https://global.bookwalker.jp/series/113007/ If you go to any volume page you'll see what information Komf can take. usually Komf will try to take all the available information from the provider

At the moment Komf can only detect volumes and not chapters
Take for example bookwalker series https://global.bookwalker.jp/series/113007/ If you go to any volume page you'll see what information Komf can take. usually Komf will try to take all the available information from the provider

Thanks for the reply!
I'm currently using Kaizoku, is there any suggested alternative to download by volumes and not chapters?
Non of my manga has volumes, so I'm assuming it's something with the way I get it?

At the moment Komf can only detect volumes and not chapters
Take for example bookwalker series https://global.bookwalker.jp/series/113007/ If you go to any volume page you'll see what information Komf can take. usually Komf will try to take all the available information from the provider

Thanks for the reply!
I'm currently using Kaizoku, is there any suggested alternative to download by volumes and not chapters?
Non of my manga has volumes, so I'm assuming it's something with the way I get it?

Basically none of the online reading sites that software like Kaizoku scrapes does per volume releases.
You'd have to either buy from somewhere like Amazon and rip them to your library yourself, or get them from other sources online.
You could also manually combine your per-chapter files into volumes by finding the chapter count per volume etc, but kaizoku would then download the missing chapters that you suddenly don't have anymore.

authors: Snd-R tomerh2001 vodkapmp

repo: Snd-R/komf


text:
Add project to OPA ecosystem listing

Not an issue really, but just found out about this project and I love the idea! 😃
Would you consider adding this integration to the OPA ecosystem page? (there's a link top-right for how to add an entry)
Also, definitely would welcome a PR to have it added to the Awseome OPA list.
Thanks!

https://github.com/open-policy-agent/opa/pull/4674 is the PR to add to the ecosystem page.
Can I add you as the signoff to pass the merge gate test?

authors: anderseknert sfc-gh-jchacon

repo: Snowflake-Labs/sansshell


text:
snowflake_function_grant: from prior state: unsupported attribute "arguments"

Provider Version
+ provider registry.terraform.io/snowflake-labs/snowflake v0.62.0

Terraform Version
Terraform v1.4.5
on darwin_arm64

Describe the bug
Dependabot proposed that we upgrade from provider version 0.56.0 to 0.62.0, and upon running terraform plan with version 0.62.0, terraform crashes with this error:
│ Warning: Failed to decode resource from state
│
│ Error decoding "module.sandbox4_application.snowflake_function_grant.application_functions_future_grant[0]" from prior state: unsupported
│ attribute "arguments"

But I'm not using any such attribute arguments:
$ terraform state show module.sandbox4_application.snowflake_function_grant.application_functions_future_grant[0]
# module.sandbox4_application.snowflake_function_grant.application_functions_future_grant[0]:
resource "snowflake_function_grant" "application_functions_future_grant" {
    database_name          = "SANDBOX4"
    enable_multiple_grants = false
    id                     = "SANDBOX4|APPLICATION||USAGE|SANDBOX4_STAFF_READ_WRITE,SANDBOX4_STAFF_READ_ONLY|false"
    on_future              = true
    privilege              = "USAGE"
    roles                  = [
        "SANDBOX4_STAFF_READ_ONLY",
        "SANDBOX4_STAFF_READ_WRITE",
    ]
    schema_name            = "APPLICATION"
    with_grant_option      = false
}

Expected behavior
terraform plan should run without crashing.

Sorry but i am not able to replicate the error you are seeing. I started with 0.56, created the future grant, then upgraded to 0.62 with no issue. I also made sure that the ID i was using was the same as yours.
Could you please try removing the resource and reimporting it?
terraform state rm snowflake_function_grant.application_functions_future_grant
terraform state import snowflake_function_grant.application_functions_future_grant "SANDBOX4|APPLICATION|||USAGE|false|true|SANDBOX4_STAFF_READ_WRITE,SANDBOX4_STAFF_READ_ONLY|"

If this issue persists, I would be happy to jump on a call to assist you.

Hi @sfc-gh-swinkler , thanks for your reply.
I tried state rm / import as requested and was able to get it to import successfully. But a subsequent terraform plan still crashed on 0.62. The crash log contained several entries like this:
Planning failed. Terraform encountered an error while generating this plan.

╷
│ Error: Plugin did not respond
│
│   with module.sandbox4_application.snowflake_database.default[0],
│   on ../../modules/aws/application/snowflake.tf line 133, in resource "snowflake_database" "default":
│  133: resource "snowflake_database" "default" {
│
│ The plugin encountered an error, and failed to respond to the plugin.(*GRPCProvider).ReadResource call. The plugin logs may contain more
│ details.

Along with other similar crashes which mention snowflake_warehouse, snowflake_storage_integration, snowflake_role, snowflake_saml_integration and snowflake_resource_monitor resources.
Then finally at the bottom of the crash log, this:
Stack trace from the terraform-provider-snowflake_v0.62.0 plugin:

panic: runtime error: index out of range [0] with length 0

goroutine 58 [running]:
github.com/Snowflake-Labs/terraform-provider-snowflake/pkg/resources.ReadResourceMonitor(0x14000a66580, {0x10384d960?, 0x14000222b60})
	github.com/Snowflake-Labs/terraform-provider-snowflake/pkg/resources/resource_monitor.go:322 +0x9cc
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).read(0x103878140?, {0x103878140?, 0x14000c8d380?}, 0xd?, {0x10384d960?, 0x14000222b60?})
	github.com/hashicorp/terraform-plugin-sdk/v2@v2.26.1/helper/schema/resource.go:712 +0x134
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).RefreshWithoutUpgrade(0x1400067b420, {0x103878140, 0x14000c8d380}, 0x140001add40, {0x10384d960, 0x14000222b60})
	github.com/hashicorp/terraform-plugin-sdk/v2@v2.26.1/helper/schema/resource.go:1015 +0x468
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*GRPCProviderServer).ReadResource(0x1400074a378, {0x103878140?, 0x14000c8d260?}, 0x140001cbdc0)
	github.com/hashicorp/terraform-plugin-sdk/v2@v2.26.1/helper/schema/grpc_provider.go:613 +0x400
github.com/hashicorp/terraform-plugin-go/tfprotov5/tf5server.(*server).ReadResource(0x140000b9360, {0x103878140?, 0x14000c8cab0?}, 0x1400014bb60)
	github.com/hashicorp/terraform-plugin-go@v0.14.3/tfprotov5/tf5server/server.go:748 +0x3e8
github.com/hashicorp/terraform-plugin-go/tfprotov5/internal/tfplugin5._Provider_ReadResource_Handler({0x103814900?, 0x140000b9360}, {0x103878140, 0x14000c8cab0}, 0x140001e0b60, 0x0)
	github.com/hashicorp/terraform-plugin-go@v0.14.3/tfprotov5/internal/tfplugin5/tfplugin5_grpc.pb.go:349 +0x170
google.golang.org/grpc.(*Server).processUnaryRPC(0x14000750000, {0x10387e580, 0x140005201a0}, 0x14000c85320, 0x14000752930, 0x1040f98d0, 0x0)
	google.golang.org/grpc@v1.53.0/server.go:1336 +0xb7c
google.golang.org/grpc.(*Server).handleStream(0x14000750000, {0x10387e580, 0x140005201a0}, 0x14000c85320, 0x0)
	google.golang.org/grpc@v1.53.0/server.go:1704 +0x82c
google.golang.org/grpc.(*Server).serveStreams.func1.2()
	google.golang.org/grpc@v1.53.0/server.go:965 +0x84
created by google.golang.org/grpc.(*Server).serveStreams.func1
	google.golang.org/grpc@v1.53.0/server.go:963 +0x290

Error: The terraform-provider-snowflake_v0.62.0 plugin crashed!

This is always indicative of a bug within the plugin. It would be immensely
helpful if you could report the crash with the plugin's maintainers so that it
can be fixed. The output above should help diagnose the issue.

I assume this is the kind of thing which will probably be blocked without a debug log or similar, especially since you can't reproduce it yourself. And I'd be happy to provide such a log, but preferably not publicly on this GitHub Issue. If debug logs or similar would be helpful here, is there a way I can get them to you privately by way of Snowflake support? (We do have an enterprise contract / enterprise support, etc.)
I'm also happy to set up a call and screenshare whatever might be needed. Please let me know how you prefer to set up a call if desired.
Thanks.

Hey 👋
Closing the issue as it's referring to the deprecated resource and we're not supporting them. Please, try to use the latest provider version with the non-deprecated resources (e.g. snowflake_grant_privileges_to_account_role). If the issue persists on the non-deprecated resource, please create a new GitHub issue. The migration guide may help during migration to the latest resources. Here's a list of the latest, non-deprecated, grant resources:
Resources
snowflake_grant_privileges_to_database_role
snowflake_grant_privileges_to_account_role
snowflake_grant_account_role
snowflake_grant_database_role
snowflake_grant_application_role (coming soon)
snowflake_grant_privileges_to_share
snowflake_grant_ownership (coming soon)
Data sources
snowflake_grants


text:
Error re-creating stream

Provider Version
0.76.0
Terraform Version
1.3.9
Describe the bug
I want to re-create an existing stream, which can be done by marking the Terraform state as tainted. Once done that the Terraform plan will say the following about the object:

 is tainted, so must be replaced

Once the plan is applied Terraform will fail with:

Error: error creating stream  err = 002002 (42710): SQL compilation error:
Object '<FQ_NAME>' already exists.

Expected behavior
Should not fail. Either it drops the stream first of uses CREATE OR REPLACE STREAM, which I can see in the activity the provider is not doing.
Code samples and commands
Please add code examples and commands that were run to cause the problem.
Additional context
Add any other context about the problem here.

Hi @elventear 👋
Sorry for the late response. We've released a new v0.98.0 version (release, migration guide) with new stream resources, based on stream type in CREATE STREAM. Please upgrade to this version and use one of the relevant resources. Note that stream is now deprecated.

Closing due to inactivity. Please create a new issue if the problem persists in the newest version.

authors: elventear sfc-gh-jmichalak


text:
[Bug]: Not possible to rename stage - Running into a deadlock

Terraform CLI Version
1.5.7
Terraform Provider Version
0.92.0
Terraform Configuration
provider "snowflake" {
  role  = "SYSADMIN"
}

terraform {
  required_version = "~> 1.5.0"
  required_providers {
    snowflake = {
      source  = "Snowflake-Labs/snowflake"
      version = "~> 0.92.0"
    }
  }
}

resource "snowflake_database" "this" {
  name = "LOCAL_TEST_DB"
}

resource "snowflake_schema" "this" {
  name     = "TESTING"
  database = snowflake_database.this.name
}

resource "snowflake_table" "table_v1" {
  database                    = snowflake_database.this.name
  schema                      = snowflake_schema.this.name
  name                        = "TEST_V1"
  change_tracking             = false

  column {
    name     = "ID"
    type     = "INTEGER"
  }

  column {
    name = "NAME"
    type = "VARCHAR(255)"
  }
}

resource "snowflake_table" "table_v2" {
  database                    = snowflake_database.this.name
  schema                      = snowflake_schema.this.name
  name                        = "TEST_V2"
  change_tracking             = false

  column {
    name     = "ID"
    type     = "INTEGER"
  }

  column {
    name = "NAME"
    type = "VARCHAR(255)"
  }
}

resource "snowflake_stage" "stage_v1" {
  name        = "TEST_V1"
  database    = snowflake_database.this.name
  schema      = snowflake_schema.this.name
}

resource "snowflake_stage" "stage_v2" {
  name        = "TEST_V2"
  database    = snowflake_database.this.name
  schema      = snowflake_schema.this.name
}

Category
category:resource
Object type(s)
resource:stage
Expected Behavior
When the provided terraform code is applied in Snowflake the Database, Schema, two tables and two named stages can be deployed successful. Everything is working as expected so far. Due to manual changes on Snowflake someone executed a rename command on one of the named stages: alter stage LOCAL_TEST_DB.TESTING.TEST_V1 rename to POST_TEST_V1;
When executing a terraform plan now in Terraform the expected behaviour would be that terraform recognizes that the defined stage no longer exists and will show a create stage in the produced plan. When this plan is executed terraform will create a new stage having the "old" name. In Snowflake there will be the renamed "old" stage and the newly created stage with the "old" name.
Actual Behavior
After a rename of an existing stage the provider runs into an error which does not longer allow for plan, apply or destroy commands.

It seems that it is missing the behaviour that the provider can differ between a describe and a show objects like function. For example for tables the described process is working completely without errors.
Steps to Reproduce

Terraform Apply with the provided code
Manually Rename one of the stages inside of Snowflake with the rename command
Try to execute terraform plan

How much impact is this issue causing?
Medium
Logs
No response
Additional Information
No response
Would you like to implement a fix?

[ ] Yeah, I'll take it 😎

Hey @JESCHO99. Thanks for reaching out to us.
We plan to rework stages soon (https://github.com/Snowflake-Labs/terraform-provider-snowflake/blob/main/v1-preparations/ESSENTIAL_GA_OBJECTS.MD). However, this seems to be an easy fix, i.e. we have to handle this error conditionally like e.g. in the schemas (we are doing it for every resource we redesign).
I should be able to squeeze it in in next week's release (if I can prove that this is really the cause as expected).

Hey @JESCHO99. I have prepared a fix in https://github.com/Snowflake-Labs/terraform-provider-snowflake/pull/3020. It will be released as part of v0.95.0 today or tomorrow (we have to wrap a few other pull requests before making the release).

Hey @sfc-gh-asawicki, huge thanks for the quick fix!

Hey @JESCHO99, we had to postpone the v0.95.0 release to Monday, sorry for the inconvenience.

Hey @JESCHO99. Did you check the fix? If so, can we close the issue?

Closing due to inactivity. Please create a new issue if the problem persists in the newest version.


text:
Fix build error in MessageManager.swift

Solves #70

You rock. Thanks!

authors: itsthisjustin rasmusbe


text:
Add possibility to specify options to child_process.spawn

In particular I need to pass {detached: true}. The reason is that when an application is interrupted by Ctrl-C, all child processes also receive SIGINT including the exiftool process. I would like to shield the exiftool process from that in order to be able to shut down my application in a controlled fashion.

@mika-fischer ok i'll do it

@mika-fischer sorry for the delay, I'll be releasing this feature tomorrow.

@mika-fischer thanks for opening this issue. The feature has landed in node-exiftool@2.3.0. Please beware that conhost.exe and a second exiftool process will be open by exiftool on Windows platform -- which you then need to kill manually if you want to handle exit gracefully. See readme and test.

authors: mika-fischer z-vr

repo: Sobesednik/node-exiftool


text:
VitamineT : ajout des appointments à l'export

US #1019
Comment tester
poetry run python scripts/export_notebook.py 1c52e5ad-e0b9-48b9-a490-105a4effaaea
Devrait produire un json de ce type :
[
    {
        "appointments": [
            {
                "account_info": {
                    "email": "pierre.chevalier@livry-gargan.fr",
                    "firstname": "Pierre",
                    "lastname": "Chevalier"
                },
                "created_at": "2021-09-21 13:06:45.076000+00:00",
                "date": "2021-09-21",
                "status": "present",
                "updated_at": "2021-09-21 13:06:45.076000+00:00"
            },
            {
                "account_info": {
                    "email": "pcamara@seinesaintdenis.fr",
                    "firstname": "Paul",
                    "lastname": "Camara"
                },
                "created_at": "2021-09-11 13:06:45.076000+00:00",
                "date": "2021-09-11",
                "status": "absent",
                "updated_at": "2021-09-11 13:06:45.076000+00:00"
            },
            {
                "account_info": {
                    "email": "pierre.chevalier@livry-gargan.fr",
                    "firstname": "Pierre",
                    "lastname": "Chevalier"
                },
                "created_at": "2021-08-11 13:06:45.076000+00:00",
                "date": "2021-08-11",
                "status": "pending",
                "updated_at": "2021-08-11 13:06:45.076000+00:00"
            }
        ],
        "beneficiary": {
            "address1": "7 chemin du soleil",
            "address2": null,
            "caf_number": "2055990",
            "city": "Livry-Gargan",
            "created_at": "2022-03-30 09:02:50.597956+00:00",
            "date_of_birth": "1982-02-01",
            "email": "stifour93@yahoo.fr",
            "firstname": "Sophie",
            "lastname": "Tifour",
            "mobile_number": "0606060606",
            "pe_number": "300000L",
            "place_of_birth": "Ch\u00e2lon en Champagne",
            "postal_code": "93190",
            "updated_at": "2022-03-30 09:02:50.597956+00:00"
        },
        "contract_end_date": null,
        "contract_sign_date": "2020-01-05",
        "contract_start_date": null,
        "contract_type": "cer",
        "created_at": "2021-09-21 11:51:37.295647+00:00",
        "education_level": "NV5",
        "focuses": [
            {
                "created_at": "2021-09-21 13:33:16.965230+00:00",
                "linked_to": "cer",
                "situations": [
                    "Pr\u00eat  \u00e0 suivre une formation"
                ],
                "targets": [
                    {
                        "actions": [
                            {
                                "action": "Orientation vers une SIAE",
                                "created_at": "2020-11-01 13:40:07.137635+00:00",
                                "status": "in_progress",
                                "updated_at": "2022-08-31 09:53:19.073615+00:00"
                            },
                            {
                                "action": "Formation certifiante",
                                "created_at": "2021-07-01 15:34:53.239372+00:00",
                                "status": "in_progress",
                                "updated_at": "2022-08-31 09:53:19.073615+00:00"
                            },
                            {
                                "action": "Avoir un pass IAE valid\u00e9",
                                "created_at": "2021-06-08 13:42:53.239372+00:00",
                                "status": "in_progress",
                                "updated_at": "2022-08-31 09:53:19.073615+00:00"
                            }
                        ],
                        "created_at": "2021-09-21 13:35:11.636378+00:00",
                        "status": "in_progress",
                        "target": "Acc\u00e9der \u00e0 l\u2019emploi",
                        "updated_at": "2022-08-31 09:53:19.073615+00:00"
                    },
                    {
                        "actions": [
                            {
                                "action": "Pr\u00e9pa-Comp\u00e9tences",
                                "created_at": "2020-09-01 15:11:37.553360+00:00",
                                "status": "in_progress",
                                "updated_at": "2022-08-31 09:53:19.073615+00:00"
                            }
                        ],
                        "created_at": "2021-09-21 13:34:17.493745+00:00",
                        "status": "in_progress",
                        "target": "D\u00e9finir ou confirmer un projet professionnel",
                        "updated_at": "2022-08-31 09:53:19.073615+00:00"
                    }
                ],
                "theme": "emploi",
                "updated_at": "2022-08-31 09:53:19.073615+00:00"
            },
            {
                "created_at": "2021-09-21 13:26:42.939011+00:00",
                "linked_to": "cer",
                "situations": [
                    "Besoin d'\u00eatre guid\u00e9 dans le cadre d'un acc\u00e8s aux droits"
                ],
                "targets": [
                    {
                        "actions": [
                            {
                                "action": "Demande de CSS",
                                "created_at": "2020-01-05 15:08:20.139704+00:00",
                                "status": "in_progress",
                                "updated_at": "2022-08-31 09:53:19.073615+00:00"
                            }
                        ],
                        "created_at": "2021-09-21 14:55:12.797276+00:00",
                        "status": "in_progress",
                        "target": "Travailler l\u2019acc\u00e8s aux droits",
                        "updated_at": "2022-08-31 09:53:19.073615+00:00"
                    }
                ],
                "theme": "difficulte_administrative",
                "updated_at": "2022-08-31 09:53:19.073615+00:00"
            },
            {
                "created_at": "2021-09-21 13:15:54.752334+00:00",
                "linked_to": "cer",
                "situations": [
                    "H\u00e9berg\u00e9 chez un tiers"
                ],
                "targets": [
                    {
                        "actions": [
                            {
                                "action": "Demande de logement social",
                                "created_at": "2020-07-01 15:13:59.820331+00:00",
                                "status": "in_progress",
                                "updated_at": "2022-08-31 09:53:19.073615+00:00"
                            },
                            {
                                "action": "Demande SIAO",
                                "created_at": "2020-01-05 13:55:43.100609+00:00",
                                "status": "in_progress",
                                "updated_at": "2022-08-31 09:53:19.073615+00:00"
                            }
                        ],
                        "created_at": "2021-09-21 13:17:53.594417+00:00",
                        "status": "in_progress",
                        "target": "Changer de logement",
                        "updated_at": "2022-08-31 09:53:19.073615+00:00"
                    }
                ],
                "theme": "logement",
                "updated_at": "2022-08-31 09:53:19.073615+00:00"
            }
        ],
        "geographical_area": "between_10_20",
        "members": [
            {
                "active": true,
                "created_at": "2021-09-21 11:51:37.295647+00:00",
                "invitation_sent_at": null,
                "last_modified_at": null,
                "last_visited_at": "2021-09-21 13:06:45.076000+00:00",
                "member_type": "referent"
            }
        ],
        "right_are": false,
        "right_ass": false,
        "right_bonus": false,
        "right_rqth": false,
        "right_rsa": "rsa_droit_ouvert_et_suspendu",
        "updated_at": "2022-03-30 09:17:52.320373+00:00",
        "wanted_jobs": [
            {
                "rome_code": {
                    "code": "A1101",
                    "description": "Conducteur / Conductrice d'engins d'exploitation agricole",
                    "label": "Conducteur / Conductrice d'engins d'exploitation agricole (A1101)"
                }
            },
            {
                "rome_code": {
                    "code": "K1304",
                    "description": "Aide \u00e0 domicile",
                    "label": "Aide \u00e0 domicile (K1304)"
                }
            }
        ],
        "work_situation": "iae",
        "work_situation_date": "2021-09-22",
        "work_situation_end_date": null
    }
]```

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

authors: SocialGroovyBot vjousse

repo: SocialGouv/carnet-de-bord


text:
Feat/#71 use authent in ds management

le territoire user est maintenant directement dans la table user : relation one to one
quand on se connecte en back, le token contient maintenant le territoire. Un middleware permet de transformer ce territoire en liste de département
avec cette liste de departement, en back, on peut savoir grace a une requete dans la table hebergement quels sont les hebergements appartenant au territoire de l'administrateur. Avec cette liste d'hebergement, on peut filtrer les demandes (requete compliquée car les hebergement de la demandes sont stockés en tant qu'id dans u json, je n'ai pas trouvé de moyen de faire une sorte de "jointure" en sql. On a claiement de la dette technique la, il va falloire vite la corriger je pense).
La regle que j'ai utilisé :

un admin voit toutes les demandes qui passe par son territoire.
si le premier hebergement appartient au territoire de l'admin, alors, il a en plus les droits d'instruire la demande, sinon, lecture seule

possibilité de filtrer et trier le tableau selon cette info

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

authors: SocialGroovyBot benjaminDNUM

repo: SocialGouv/vao


text:
Error: TypeError: buf.copy is not a function

Just working on a fresh project using socketcluster create lab1 and getting loads of errors in the server output
1454070786007 - Origin: Balancer
    Error: TypeError: buf.copy is not a function
    at Function.Buffer.concat (buffer.js:239:9)
    at IncomingMessage.<anonymous> (/path/to/lab1/node_modules/socketcluster/lib/scbalancer.js:306:31)
    at emitNone (events.js:72:20)
    at IncomingMessage.emit (events.js:166:7)
    at endReadableNT (_stream_readable.js:905:12)
    at nextTickCallbackWith2Args (node.js:474:9)
    at process._tickDomainCallback (node.js:429:17)
   >> Balancer PID: 2779

Am on node 5.4.1 if that helps

@poppahorse Which version of SC are you using? Version 1.x.x?

Sorry should have mentioned that too. Freshly installed via npm so 1.3.2

Closing. Dropping support for version 1 of SC.

@poppahorse Ran into the same problem. Switch to node v0.10.44 (use nvm if you like) and seems fine now. 4.2 had same problem as 5.x.

authors: jondubois poppahorse stewartcelani

repo: SocketCluster/socketcluster


text:
Add a way for package maintainers to specify their own overrides

In developing Socket Registry I have been noodling on giving package maintainers the ability to specify their own overrides. So we can include them where it makes sense (in our registry/manifest.json). \cc @ljharb
I'd like the data to be accessible via the npm registry. We query the registry to create the manifest per package looking for things like "deprecated". Let's keep it simple. If a version is released with a prerelease of "override" we can defer to it for some category of overrides, like "cleanup".

I'd like the data to be accessible via the npm registry. We query the registry to create the manifest per package looking for things like "deprecated". Let's keep it simple. If a version is released with a prerelease of "override" we can def to it for some category of overrides, like "cleanup".

@ljharb do you want to test the waters with this? Maybe pick an easier/simple package and try it out.

The use cases I think are good to handle are:

a different version of the same package is the replacement (either a prerelease range, or a major range, or a dist-tag)
an entirely different package is the replacement (replace foo with bar@^1 eg)
a scope is the replacement (replace foo with @ljharb-cleanups/foo, or something, same version numbers)

The third one is a bit too complex but I thought it was worth mentioning anyways.
A possible approach that could handle the first two is a new top-level key, say "variants". The LHS of this object is a category, like "cleanup", or an arbitrary string. The RHS is the same as the RHS of an overrides object.
So, for a concrete scenario:

I have call-bind v1, which by default uses function-bind, grabs a bunch of intrinsics, and is CJS.
I could create an ESM version that assumes bind and Object.defineProperty and Reflect.apply exist, and publish it as a prerelease of v2, like v2.0.0-cleanup.0
then on v1, i publish package.json with variants: { cleanup: '^2.0.0-cleanup' } or similar, and this tool can automatically pick that up

Alternatively:

I have call-bind v1, which by default uses function-bind, grabs a bunch of intrinsics, and is CJS.
I could create an ESM version that assumes bind and Object.defineProperty and Reflect.apply exist, and publish it as call-bind-modern
then on v1 of call-bind, i publish package.json with variants: { cleanup: 'call-bind-modern@^1' } or similar, and this tool can automatically pick that up

Thoughts?

So the key is metadata in your package.json. Our socket overrides have a socket field in their package.json so I can dig that. I like storing it there so we can query and spot it. Enter bikeshed of what to call it. Let's say "variants" for now. A tag used for the name of the variant and a reference. I believe npm does it like npm:call-bind-modern@^1. That could work! Then any tool looking for a variant and a tag can do what they want with the info. We have a thing (cleanup) and a replacement (npm:call-bind-modern@^1).

exactly - and i can make up my own variants if i want, and tools can choose to adopt them if they want.

Okay. Let's roll with "variants". ChatGPT could not come up with a better name 🙃 🤣

@ljharb This is next on my plate to take on. There's an easy way and a less easy way to detect this. One is looking at the packages already in the node_modules folder and the other is querying the registry to get the latest version and extract the package.json to inspect.

Presumably it'd be in the packument, so you wouldn't have to extract anything? (there's no risk here imo from packument confusion)

From the outside looking in (so building something outside of npm) I don't think we'll get the info from the packument. Long-term if it becomes a thing then that would be nice for sure.

Why wouldn't you want to, since it's much cheaper than extracting the archive?

Oh I want to, it just requires moving npm I believe, unless we can already do this today without patching the packument format.

Excellent

authors: jdalton ljharb

repo: SocketDev/socket-registry


text:
IPSec/L2TP work with CA?

Are there plans to get certificate based authentication over IPSec/L2TP working?

Nop. But it is a nice feature

Already supported.

authors: domosekai moatazelmasry2 worship

repo: SoftEtherVPN/SoftEtherVPN


text:
Update README.md

fixed the live demo link
fixes #701 and #709

Closing because we've rebranded since then and the demo link is also different now

repo: SoftwareBrothers/adminjs


text:
Display report failure messages when status == 'failed'

probably need to address #134 and #170 first

With changes to core, in 1.0 beta 4, this should be solved


text:
⚠ SolarOscp has degraded performance

In 9d3572f, SolarOscp ($SOLAROSCP_URL) experienced degraded performance:

HTTP code: 200
Response time: 228 ms

Resolved: SolarOscp performance has improved in 0bc1e36 after 9 minutes.

repo: SolarNetworkFoundation/upptime